1 / 10
Download Presentation

Requirement model

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. Requirement model

  2. Requirement Model • To capture the functional requirements • Describe how a potential user will use the system • End users are involved Analysis Process Requirement Model Analysis Model

  3. Requirement Model • Determined by the customer’s functional requirements • Delimit the system and define its functionality • Actor constitutes the environment and use cases tell what take place in the system. • Contract between developer and the customer.

  4. Requirement Model • Determined by the customer’s functional requirements • Delimit the system and define its functionality • Actor constitutes the environment and use cases tell what take place in the system. • Contract between developer and the customer.

  5. Requirement Model • A use case model: Specify the functionality the system has to offer from a user’s perspective. • User Interface description: specify what the user interface will look like when the use cases are performed. • A problem domain object model: to give a conceptual picture and better understanding of the system, objects are used to represent occurrences in problem domain.

  6. Requirement Model • A use case model uses actors and use cases as explained in previous slides.

  7. Requirement Model User Interface description: When describing the use cases with the users- describe the interfaces in detail. • If Man-Machine Interface (MMI) : • use sketches of what the user will see on the screen performing the use case • provide more sophisticated simulations using a User interface management system (UIMS). • Other system interfaces such as communication protocol that must be standardized are defined.

  8. Requirement Model Example: • Customer Interface • Customer panel including Buttons, Holes, Alarm devices • Receipt layout • Operator interface: • For changing information, resetting alarm, request day summaries and so on.......

  9. Requirement Model Problem domain objects • Object Name • Logical Attributes • Static instance association(static reference to an object ) • Inheritance • Dynamic instance association(Object can stimuli other) • Operations

  10. Requirement Model Problem domain objects • Advantage of problem domain model: • Support for understanding a system in more detail. • Support formulation of use case description and MMI design.

More Related