TAILIEUCHUNG - Lecture Enterprise systems development - Lecture 7

One objective of this chapter is to explain how to unite the business process level REA models for multiple transaction cycles. A second objective is to explain implementation compromises commonly made at each step in conceptual modeling and database design. A final objective of this chapter is to demonstrate retrieval of information from multiple integrated business processes. | Lecture 7 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science 1 Requirements Analysis Analysis Checklists Analysis Checklists Requirements Interactions Interaction Metrices Requirements Negotiation Negotiation Meetings Requirements Documentation/Specification Characteristics of Requirements Correct Consistent Unambiguous Complete Feasible Relevant Testable Traceable Examples of Poorly Written Requirements ATM machine will confiscate the card if user enters wrong PIN multiple times. The product should have a good human interface. The output of the program shall usually be given within 10 secs. The System shall allow student to add six courses in one semester if he/she has good GPA. 12 Requirements specification (1) The System Requirements Definition Document A statement in a natural language of what user services the system is expected to provide. sometimes known as the user requirements document (or concept of operations) records the system requirements. defines the high-level system requirements from the domain perspective. Must list the system requirements along with background information about overall objectives for the system, its target environment and a statement of the constraints, assumptions and non-functional requirements. May include conceptual models designed to illustrate the system context, usage scenarios, the principal domain entities, and data, information and work-flows. 13 Requirements specification (2) Requirements specification (intermediate level) A structured document which sets out the system services in more detail. It should be written such that understandable by technical staff from both clients and developers. Samples/Template Sample Table of Contents Preamble Requirement Shell Requirement Numbering Definitions Used in this Template PROJECT DRIVERS: 1. The Purpose of the Product 2. Client, Customer, Stakeholders 3. Users of the Product PROJECT .

• Kỹ thuật lập trình
• Enterprise systems development
• Lecture Enterprise systems development
• Enterprise systems
• Requirements engineering
• Software Architecture
• Software quality