Requirements engineering processes Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
4.5 Requirements elicitation and analysis
After an initial feasibility study, the next stage of the requirements engineering process is requirements elicitation and analysis. In this activity, software engineers work with customers and system end-users to find out about the application domain, what services the system should provide, the required performance of the system, hardware constraints, and so on. 4.5 ■ Requirements elicitation and analysis 101Parts
» Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» COLLEAGUES — Software engineers shall be fair to and supportive of their colleagues.
» Case studies Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software process models Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Process activities Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Coping with change Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» The Rational Unified Process
» Agile methods Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Plan-driven and agile development
» Extreme programming Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Agile project management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Scaling agile methods Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Functional and non-functional requirements
» The software requirements document
» Requirements specification Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Requirements elicitation and analysis
» Requirements validation Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Requirements management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Context models Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Interaction models Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Structural models Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Behavioral models Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Model-driven engineering Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Architectural views Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Architectural patterns Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Application architectures Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Object-oriented design using the UML
» Design patterns Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Implementation issues Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Open source development Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Development testing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Test-driven development Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Release testing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» User testing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Evolution processes Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Program evolution dynamics Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software maintenance Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Legacy system management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Complex systems Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Systems engineering Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» System procurement Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» System development Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» System operation Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Dependability properties Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Safety Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Security Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Safety specification Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Reliability specification Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Security specification Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Formal specification Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Redundancy and diversity Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Dependable processes Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Dependable programming Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Give four reasons why it is hardly ever cost effective for companies to ensure that their
» Explain why it is reasonable to assume that the use of dependable processes will lead to the
» Give two examples of diverse, redundant activities that might be incorporated into
» What is the common characteristic of all architectural styles that are geared to supporting
» Imagine you are implementing a software-based control system. Suggest circumstances in
» You are responsible for the design of a communications switch that has to provide 247
» ‘Agile Software Development in Large Organizations’. IEEE Computer, 37 12, 26–34.
» Security risk management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Design for security Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» System survivability Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Static analysis Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Reliability testing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Security testing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Process assurance Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Safety and dependability cases
» The reuse landscape Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Application frameworks Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software product lines Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» COTS product reuse Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Components and component models
» CBSE processes Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Component composition Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Distributed systems issues Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Client–server computing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Architectural patterns for distributed systems
» Services as reusable components
» Service engineering Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software development with services
» Embedded systems design Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Timing analysis Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Real-time operating systems Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Using examples, explain why real-time systems usually have to be implemented using
» Identify possible stimuli and the expected responses for an embedded system that controls a
» Using the state-based approach to modeling, as discussed in Section 20.1.1, model the
» Explain why an object-oriented approach to software development may not be suitable for
» Show how the Environmental Control pattern could be used as the basis of the design of a
» Design a process architecture for an environmental monitoring system that collects data from
» Emergency service users Software engineering with aspects
» Emergency planners Software engineering with aspects
» Maintenance staff Software engineering with aspects
» Risk management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Managing people Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Teamwork Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software pricing Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Plan-driven development Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Project scheduling Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Agile planning Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Estimation techniques Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» A software manager is in charge of the development of a safety-critical software system, which
» Software quality Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software standards Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Reviews and inspections Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Software measurement and metrics
» Assume you work for an organization that develops database products for individuals and
» Explain why program inspections are an effective technique for discovering errors in a
» Explain why design metrics are, by themselves, an inadequate method of predicting
» Explain why it is difficult to validate the relationships between internal product attributes,
» A colleague who is a very good programmer produces software with a low number of
» Change management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Version management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» System building Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Release management Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Describe five factors that should be taken into account by engineers during the process of
» The process improvement process
» Process measurement Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
» Process analysis Software Engineering 9th ed (intro txt) I. Sommerville (Pearson, 2011)
Show more