1 / 20

Review 1

Review 1. Phase II report -1. Due on 2/24 On top of Phase I report 5-15 pages in total (together phase I report) Free style in writing (use 11pt font or larger) Focus on requirements Description of related activities, e.g., interviews with stakeholders

jacintat
Download Presentation

Review 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Review 1

  2. Phase II report -1 • Due on 2/24 • On top of Phase I report • 5-15 pages in total (together phase I report) • Free style in writing (use 11pt font or larger) • Focus on requirements • Description of related activities, e.g., interviews with stakeholders • Describe functional and nonfunctional requirements

  3. Phase II report -2 • Provide scenarios or use-cases • Provide requirements management planning • Feasibility studies • Draw at least 2 models if applicable • Context models • Data-flow model • State machine models • Inheritance models • Object aggregation models • Object behaviour model

  4. Exam 1 • Thursday, 2/17/05 • 1-hour •  closed book • Chapters 1-8 • 20% of your total grade

  5. Exam topics -1 • Chapter 1  • Software engineering vs. system engineering • Software process • Software cost • Chapter 2  • Socio-technical systems • Emergent properties of a system • Sub-systems • Legacy system

  6. Exam topics -2 • Chapter 3 • Critical system • Reliability and availability • Safety and security • Chapter 4 • Waterfall model • Evolutionary development • Exploratory development and throw-away prototype • Component-based development • Process iteration • Rational unified process • CASE tool

  7. Exam topics -3 • Chapter 5 • Project planning • Milestones • Deliverables • Project scheduling • Bar charts and activity networks • Risk management

  8. Exam topics -4 • Chapter 6 • User requirements • Systemrequirements • Functional/non-functional requirements • Domain requirements • Requirement documents

  9. Exam topics -5 • Chapter 7 • Stakeholders • Viewpoints • Feasibility studies • Scenarios • User cases • Prototyping • Requirement validation • Requirement management

  10. Exam topics -6 • Chapter 8 • Context model • Architectural model • Behavioral model • Data-flow models • State machine models • Data models • Object inheritance model • Object aggregation model • UML

  11. Sample exam questions - 1 • 1. Are the following statements about the software requirements document true or false? (1) Software engineering is only useful for those who become software engineers. (2) The requirements document should not specify responses to undesirable events.

  12. Sample exam questions - 2 • 2. Multiple choices • (1) In system modeling, a ___________ model shows the system’s reaction to events. A. Context B. Architectural C. Stimulus/response D. Data Processing

  13. Sample exam questions - 2 • (2) System Requirements are A. A detailed list of services and constraints of a proposed system B. A natural language statement of the functionality a system should provide C. A list of basic requirements the system must meet to run the software D. Not on this test (wishful thinking) E. None of the above

  14. Sample exam questions - 3 • (3) User Requirements are A. A detailed list of services and constraints of a proposed system B. A natural language statement of the functionality a system should provide C. A list of basic requirements the user must meet before using a given system D. Not condoned by my religion E. None of the above

  15. Sample exam questions - 4 • 3. Short answers  • (1) Describe the waterfall model of software development. What are some of its advantages and disadvantages? What alternatives exist? • (2) What type of UML diagram is used to describe a specific scenario of a use case? • (3) What is the difference between evolutionary and throw-away prototyping? • (4) What is one major difference between System Engineering and Software Engineering, as disciplines?

  16. Sample exam questions - 5 • (5) What is the purpose of upper-CASE tools? • (6) Give one specific example of a possible emergent property of a nuclear power plant. State the property as a requirement. • (7) Give one specific example of an organizational non-functional requirement of each variety below. • (a) Delivery: • (b) Implementation: • (c) Standards:

  17. Sample exam questions - 6 • (8) Identify four potential stakeholders of a point-of-sale system at a gasoline fuel pump. • (9) Why is traceability an important aspect of requirements management? • (10) Give one reason why context system models are useful for requirements validation. • (11) Which style of prototyping is most appropriate when the requirements are not well-understood?

  18. Sample exam questions - 7 • 4. Match each system to the most appropriate model and briefly justify your decision. • Software Process Models • A. Waterfall Model • B. Evolutionary Development • C. Reuse-oriented Development • __3D modeling and animation software designed to have a revolutionary user interface and novel algorithms for creating surreal scenes __A shopping cart module for a website that needs to be up and running with basic functionality within a week __Implementation of a Linux driver for a hardware device where full specifications are available from the manufacturer

  19. Functional requirement Non-functional requirement Definition List the requirements (three for each type) for a university library system Sample exam questions - 8 • 6. Describe functional and non-functional requirements in the following categories.

  20. Task Duration (days) Dependencies T1 10 T2 10 T1 T3 15 T4 5 T1,T3 T5 15 T2 T6 15 T3 T7 15 T8 15 T3,T4,T5 T9 35 T7 T10 20 T4,T6 T11 10 T9 T12 20 T10 T13 15 T4,T5 T14 10 T11,T8 T15 20 T12,T14 T16 15 T13,T15 Sample exam questions - 9 The accompanying table sets out a number of activities, durations, and dependencies. Draw an activity chart and identify the critical path(s). What is the length of the critical path? What is the maximum number of days that T4 can be delayed without impacting the finish date?

More Related