Homework answers / question archive / SYSE 620 Final Exam Question 1: Which of the following is likely to be part of a software project team (highlight all that apply)

SYSE 620 Final Exam Question 1: Which of the following is likely to be part of a software project team (highlight all that apply)

Computer Science

Share With

---

SYSE 620 Final Exam

Question 1:

Which of the following is likely to be part of a software project team (highlight all that apply).

• account managers
• analysts
• Chief Executive Officer
• Chief Operating Officer
• developers
• human resources
• Information Systems Security Officer
• project manager
• quality assurance personnel
• sales representatives
• users or their representatives

Question 2:

Align the motivation and expertise areas to the stakeholder (enter the numbers or letters in the appropriate location):

Stakeholder	Motivation	Expertise areas
Customer
User
Project manager
Analyst
Developer
Quality assurance

 

Motivation:

1. Ensure compliance to process and product standards
2. Introduce change with maximum benefit
3. Introduce change with minimum disruption
4. Produce technically excellent system, use latest technologies
5. Specify requirements on time and within budget
6. Successfully complete the project with the given resources

Expertise areas:

1. Business and information system strategies, industry trends
2. Business process, operating procedures
3. Latest technologies, design methods, programming environments and languages
4. Project management, software development and delivery process
5. RE methods and tools
6. Software process, methods, and standards

Question 3:

Which of the following are not reasons for changing requirements (highlight all that apply)?

1. incompletely captured requirements
2. over specification, under specification
3. on budget
4. changing threats during systems development
5. engineers rushing through the requirements engineering process
6. within scope
7. technology changes
8. personnel changes
1. scope creep

Question 4:

Is the following a good or bad requirement? Explain why it is a good or bad requirement:

• “Shut off the pumps if the water level remains above 100 meters for more than 4 seconds.”

Question 5:

(True or False) CM is used as an engineering management process to control the variance (dynamic changes) of the product and its engineering data (design documents, project documents, etc.) over the time.

Question 6:

Align the descriptions and practices with the Requirements Engineering Maturity Levels

	Level 0	Level 1	Level 2	Level 3
Description
Practices

 

Descriptions:

1. At this maturity level, requirements are elicited, analyzed, prioritized, documented, verified and validated; requirements changes are managed, requirements traceability is maintained; and requirements status tracking is established to the extent that it can demonstrate that all requirements have been implemented. In addition, requirements are allocated among product releases and components, and inconsistencies between requirements and the project work products related to the RE process are identified and resolved.
2. A defined RE process clearly states the process purpose, assumptions, related standards, policy, what activities are carried out, the structuring or schedule of these activities, who is responsible for each activity, the inputs and outputs to/from the activity, what resources are allocated, and the tools used to support the RE process.
3. An incomplete RE process is a process that either is not performed or partially performed. This means one or more of the RE practices are not implemented. There is no RE goal exists for this level since there is no reason to institutionalize a partially performed RE process.
4. At this maturity level, the RE process is planned, institutionalized for consistent performance, and executed in accordance with policy; involves relevant stakeholders; allocated with adequate resources; people are trained with the appropriate skills; RE process is monitored, controlled and reviewed; RE process work products are placed under appropriate levels of control; RE process adherence is evaluated; and RE status is reviewed by higher management. The process discipline reflected by this RE maturity level helps to ensure that existing RE practices are retained even during time of stress.

 

Practices:

1. Allocate Requirements
2. Analyze Requirements to Achieve Balance
3. Analyze Requirements
4. Assign Responsibility
5. Collect Improvement Information
6. Conduct Requirements Elicitation
7. Develop the Customer Requirements
8. Develop the Product Specifications
1. Establish a Defined RE Process
10. Establish a Standard Requirements Document Structure
11. Establish an Organizational Requirements Engineering Policy
50. Identify and Involve Relevant Stakeholders
1000. Identify Inconsistencies between Project Work and Requirements
14. Manage Configurations
15. Manage Requirements Changes
16. Manage Requirements Traceability
17. Model Requirements
18. Monitor and Control the RE Process
19. Objectively Evaluate Adherence
20. Obtain an Understanding of Requirements
21. Obtain Commitment to Requirements
5. Plan the Requirements Engineering Process
23. Prioritize Requirements
10. Provide Adequate Resources
25. Review Status with Higher Level Management
26. Train People
1. Validate Requirements
28. Verify Requirements

Question 7:

CMMI Five Levels of Maturity

Put the maturity levels in the appropriate position in the table along with the associated characteristics for that level.

Level	1	2	3	4	5
Level Name
Characteristics

 

Level Names:

1. Managed
2. Optimizing
3. Repeatable
4. Initial
5. Defined

Characteristics:

1. Attention is paid to documentation, standardization and integration
2. Detailed, quantitative measurements of process and product quality are collected
3. Pilot projects are common
4. Processes are ad hoc, chaotic and disorganized
5. Processes are continuously improving
6. Processes are defined and documented
7. Processes are predictable
8. Projects follow this defined process, even under schedule pressures
9. Successes can be repeated
10. There are few formal rules or procedures

Question 8:

(True or False) The following are six major purposes that requirements serve in traditional systems engineering.

• Contract bounds
• In-process verification
• System verification
• Allocation
• Analysis
• Agreement

Question 9:

Which of the following are shortcomings in creating good requirement documents (highlight all that apply)?

• Being filed but never referenced
• Distribute the entire requirements document once it is completed, reviewed, and approved.
• Having conflicting content
• Having no change control
• Having one person compile the document
• Identify specific reviewers and approvers of the requirements document
• Prepare drafts, not final copies, for review
• Provide sufficient time for review
• Providing insufficient data
• Replying on too few or the wrong people
• Using diagrams to support narrative text

Question 10:

(True or False) The following guidelines should be kept in mind as software requirements are documented.

• Keep sentences and paragraphs short. Use the active voice. Use proper grammar, spelling, and punctuation. Use terms consistently and define them in a glossary or data dictionary. 
• To see if a requirement statement is sufficiently well defined, read it from the developer’s perspective.
• Requirement authors often struggle to find the right level of granularity. Avoid long narrative paragraphs that contain multiple requirements. A helpful granularity guideline is to write individually testable requirements.
• Watch out for multiple requirements that have been aggregated into a single statement. Conjunctions like "and" and "or" in a requirement suggest that several requirements have been combined. Never use "and/or" in a requirement statement. 
• Write requirements at a consistent level of detail throughout the document.
• Avoid stating requirements redundantly in the document. While including the same requirement in multiple places may make the document easier to read, it also makes maintenance of the document more difficult.