Software Process

Question 1

Waterfall software process

Answer 1

Requirements: product requirements document 
Design: software architecture 
Implementation: software
Verification:
Maintenance:

Question 2

Accidental complexity

Answer 2

Relates to problems which engineers create and can fix

Ex) the details of writing and optimizing code

Question 3

Essential complexity

Answer 3

Is caused by the problem to be solved and relate to the complexity of context and stakeholders involved

Question 4

Problem of requirements

Answer 4

• difficult to communicate clearly
• difficult to document
• difficult to negotiate
• difficult to manage (change)

Question 5

Success Factors in 1995

Answer 5

1. User involvement
2. Executive management support
3. Clear statement of requirements
4. Proper planning
5. Clear vision and objectives

Question 6

Success factors 2015

Answer 6

1. Execute sponsorship
2. User Involvement
3. Agile process
4. Modest execution
5. Clear business objectives

Question 7

Importance of software process

Answer 7

Project success
Financial
Safety

Question 8

Mitigate project risks

Answer 8

• continuous access to stakeholders
• incremental and iterative software development
• having cycles instead of steps

Question 9

Waterfall vs agile

Answer 9

• waterfall does each step then done, not used anymore
• agile has a cycle of testing and coding (working with stockholder) better method (ex scrum and spring planning in scrum)

Question 10

Model, view, controller

Answer 10

• segment our ideals from the model (sep how we interact with it to how we view it)
• benefits: to make changes you know where to go and don’t have to change everything, easier to test components
• downsides: disperse function into three parts and makes it hard to find code, takes over code and takes away flexibility

Question 11

Module cohesion

Answer 11

The extent to which software entities pertaining to the same functionality are contained within a single module

Question 12

Inter-module coupling

Answer 12

The extent of inter-module connections

Question 13

Architecture quality attributes

Answer 13

Want low coupling and high cohesion

-results in easier maintenance of code, higher modifiability, and localization of changes

Question 14

Categories of requirements

Answer 14

1. Functional requirements: what the software should do
2. Quality requirements: qualifications (speed, reliability, …)
3. Constraints: coming from somewhere (programming language, platform)

Question 15

Role of architecture

Answer 15

1. Functional requirements: ability of system to do work it was required
2. Quality requirement: satisfied by quality of the system as a whole

Question 16

Functionality

Answer 16

-the ability of the system to do the work for which was intended
-has the strangest relationship with architecture
Eg) “when user presses the green button something happens”

Question 17

Quality requirements

Answer 17

Pertain to the functions of a system
Eg) how quickly does the dialog appear (performance)
How often will func fail (availability)
(Usability)

Question 18

Two categories of QA’s

Answer 18

• ones that describe property of the system at runtime (availability, performance, usability)
• ones that describe some property of development of the system (modifiability, testability)

Question 19

Problems with QA’s

Answer 19

1. Testability: many quality attributes are difficult to test
2. Mapping of concern: is a system failure due to a denial-of-service attack an aspect of availability, an aspect of performance, an aspect security or usability

Question 20

Storyboarding

Answer 20

Powerful validation technique

-always them to see if it looks and flows the way it should

Question 21

V & V activities through development

Answer 21

• Requirement: rapid prototyping
• Specification: do conform to req and any ambiguity
• Design: design checked for faults
• Implementation: tested and walk through (black-box~ don’t care about implementation white-box ~ do)
• Integration: work in things independent and can be brought together
• Product Testing: look at specs and start to check boundary’s outside spec
• Acceptance Testing: software given to client to test