LlosengCh04E2

LlosengCh04E2 - Object-Oriented Software Engineering...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 4: Developing Requirements 1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 4.1 Domain Analysis The process by which a software engineer learns about the domain to better understand the problem: The domain is the general field of business or technology in which the clients will use the software A domain expert is a person who has a deep knowledge of the domain Benefits of performing domain analysis: Faster development Better system Anticipation of extensions
Background image of page 2
3 Domain Analysis document A. Introduction B. Glossary C. General knowledge about the domain D. Customers and users E. The environment F. Tasks and procedures currently performed G. Competing software H. Similarities to other domains
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Requirements must be determined Clients have produced requirements New development Evolution of existing system A B C D 4.2 The Starting Point for Software Projects green field project
Background image of page 4
5 4.3 Defining the Problem and the Scope A problem can be expressed as: A difficulty the users or customers are facing, Or as an opportunity that will result in some benefit such as improved productivity or sales. The solution to the problem normally will entail developing software A good problem statement is short and succinct
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Defining the Scope Narrow the scope by defining a more precise problem List all the things you might imagine the system doing Exclude some of these things if too broad Determine high-level goals if too narrow Example: A university registration system Initial list of problems with very broad scope Narrowed scope Scope of another system exam scheduling room allocation fee payment browsing courses registering exam scheduling room allocation fee payment browsing courses registering
Background image of page 6
7 4.4 What is a Requirement ? It is a statement describing 1) an aspect of what the proposed system must do, or 2) a constraint on the system’s development. In either case it must contribute in some way towards adequately solving the customer’s problem; the set of requirements as a whole represents a negotiated agreement among the stakeholders. A collection of requirements is a requirements document .
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
8 4.5 Types of Requirements Functional requirements Describe what the system should do Software Quality requirements C onstraints on the design to meet specified levels of quality Platform requirements C onstraints on the environment and technology of the system Process requirements C onstraints on the project plan and development methods
Background image of page 8
9 Functional Requirements What inputs the system should accept What outputs the system should produce What data the system should store that other systems might use What computations the system should perform The timing and synchronization of the above
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Software Quality Requirementts All must be verifiable Examples: Constraints on Response time Throughput Resource usage Reliability Availability
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 38

LlosengCh04E2 - Object-Oriented Software Engineering...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online