IT 313 - M1 Software Products & M2 Software Disasters

0.0(0)
studied byStudied by 14 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/36

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

37 Terms

1
New cards

Software products are generic software systems that provide functionality that is useful to a range of customers. (T/F)

True

2
New cards

The starting point for the product development is a set of ‘software requirements’ that are owned by an external client and which set out what they want a software system to do to support their business processes. (T/F)

False - The starting point for the SOFTWARE development is a set of ‘software requirements’ that are owned by an external client and which set out what they want a software system to do to support their business processes.

3
New cards

Differentiate Project-based Soft. Engr. vs Product Software Engr.

Product-based software is developed to exploit a business opportunity and sold to many customers, with the company controlling features, timeline, and updates for rapid market capture.

Project-based software is developed to meet a specific client’s requirements, with the client owning the requirements, often changing them, and the contractor maintaining the system over its long lifetime.

4
New cards

Product Based or Project Based
- The company who identified the opportunity design and implement a set

of software features that realize the opportunity and that will be useful to

customers.

Product Based

5
New cards

Product Based or Project Based
- The customer may change the requirements at any time in response to

business changes (they usually do). The contractor must change the

software to reflect these requirements changes.

Project Based

6
New cards

A set of software products that share a common core. Each member of the

product line includes customer-specific adaptations and additions.

A. Software product line
B. Platform
C. Stand-alone
D. Hybrid
E. Software service



A. Software product line

7
New cards

The software executes entirely on the customer’s

computers.

A. Software product line
B. Platform
C. Stand-alone
D. Hybrid
E. Software service

C.

8
New cards

Part of the software’s functionality is implemented on the

customer’s computer but some features are implemented on the product

developer’s servers.

A. Software product line
B. Platform
C. Stand-alone
D. Hybrid
E. Software service

D.

9
New cards

All of the product’s features are implemented on the

developer’s servers and the customer accesses these through a browser

or a mobile app.

A. Software product line
B. Platform
C. Stand-alone
D. Hybrid
E. Software service

E.

10
New cards

Comparable software development Individuals or student groups develop software as part of their course. Given an assignment, they decide what features to include in the software.

Student projects

11
New cards

Comparable software development

Researchers develop software to help them answer

questions that are relevant to their research.

Research software

12
New cards

Comparable software development

Software developers may develop tools to support

their work - in essence, these are internal products that are not intended for

customer release.

Internal tool development

13
New cards

• FOR (target customer)

• WHO (statement of the need or opportunity)

• THAT

• UNLIKE

• OUR PRODUCT

• WHY

• HOW

Which doesn’t belong to the group?

WHY & HOW

14
New cards

The product developers may work in a particular area (say marketing and sales) and

understand the software support that they need.

A. Domain experience
B. Product experience
C. Customer experience
D. Prototyping and playing around

A.

15
New cards

Users of existing software (such as word processing software) may see simpler and better ways of providing comparable functionality and propose a new system that implements this.

A. Domain experience
B. Product experience
C. Customer experience
D. Prototyping and playing around

B.

16
New cards

The software developers may have extensive discussions with prospective customers of the product to understand the problems that they face, constraints, such as interoperability, that limit their flexibility to buy new software, and the critical attributes of the software that they need.

A. Domain experience
B. Product experience
C. Customer experience
D. Prototyping and playing around

C.

17
New cards

Developers may have an idea for software but need to develop a better understanding of that idea and what might be involved in developing it into a product. They may develop a prototype system as an experiment and ‘______’ with ideas and variations using that prototype system as a platform.


A. Domain experience
B. Product experience
C. Customer experience
D. Prototyping and playing around

D

18
New cards

It is a business activity that focuses on the software products developed and sold by the business.  

Software product management

19
New cards

_________________ take overall responsibility for the product and

are involved in planning, development and product marketing. They are also the interface between the organization, its customers and the software development team. They are involved at all stages of a product’s lifetime from initial conception through to withdrawal of the product from the market.

Product managers (PMs)

20
New cards

(T/F)

Product managers must look inward to customers and potential

customers rather than focus on the software being developed.

F - Outward

21
New cards

Product management concerns

PMs have to ensure that the software being developed

meets the business goals of the software development company.

A. Business needs
B. Technology constraints
C. Customer experience

A.

22
New cards

Product management concerns

PMs must make developers aware of

technology issues that are important to customers.

A. Business needs
B. Technology constraints
C. Customer experience

B

23
New cards

What are the two demonstrations in a two-stage prototyping?

Feasibility demonstration & Customer demonstrations

24
New cards

Two-stage prototyping

You create an executable system that

demonstrates the new ideas in your product. The aims at this stage are

to see if your ideas actually work and to show funders and/or company

management the original product features that are better than those in

competing products.

Feasibility demonstration

25
New cards

Two-stage prototyping

You take an existing prototype created to

demonstrate feasibility and extend this with your ideas for specific

customer features and how these can be realized. Before you develop

this type of prototype, you need to do some user studies and have a

clearer idea of your potential users and scenarios of use.

Customer demonstration

26
New cards

(T/F)

A software used to analyze disaster reported increased suicide rates after sever natural disasters. A programming error caused the number of suicides for one year to be doubled, which was enough to throw off the entire study.

T - Disastrous Study (1999)

27
New cards

(T/F)
In the 1960s, Concept of software engineering, like hardware engineering, began to be introduced in software development projects

F - 1950s

28
New cards

(T/F)
1960s was the time where software crisis and coding first and correction later was prevalent

T -
1960s:

• “Software crisis”

• “Coding first and correction later”

• Forma techniques were less usable to general software developers

• Waterfall method was expensive and slow to implement

29
New cards

(T/F)
During the 1990s, Agile methodology was comprehensively adopted to effectively respond to rapid changes in the software market

T

30
New cards

Enumerate the four key elements of software engineering

1. Method

2. Tool

3. Procedure

4. People

31
New cards

This key element is centered on a specific language, graphical notation, are introduced from time to time

  1. Method

32
New cards

This key element refers to an automated or semi-automated method that is used to improve productivity or consistency when performing a task

2. Tool

33
New cards

This key element defines the applied method, required deliverables, controls to guarantee quality and assist coordinate adjustment, and the sequence of milestones that enable soft. managers to evaluate progress

Procedure

34
New cards

Four Key Elements of Software Engineering

As many tasks are performed by employees and organizations specializing in software engineering, software engineering relatively depends more heavily on people

People

35
New cards

Enumerate the 6 parts of the Software Development Life Cycle

● Requirements Analysis

● Design

● Implementation and Unit Testing

● Integration

● System Testing

● Deployment and Maintenance

36
New cards
37
New cards