Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Enterprise systems development (CSC447) - Lecture 5

The primary objective of this chapter is to describe a procedure for converting a conceptual business process level REA model into a logical relational database model and then into a physical Microsoft Access database implementation. This process involves a relatively straightforward set of rules that could even be programmed as an algorithm so that a computer could accomplish the conversion. This chapter also discusses data entry issues. | Lecture 5 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science 1 Requirements document structure IEEE/ANSI 830-1993 standard proposes a structure for software requirements documents 1. Introduction 1.1 Purpose of requirements document 1.2 Scope of the product 1.3 Definitions, acronyms and abbreviations 1.4 References 1.5 Overview of the remainder of the document Requirements document structure 2. General description 2.1 Product perspective 2.2 Product functions 2.3 User characteristics 2.4 General constraints 2.5 Assumptions and dependencies 3. Specific requirements Covering functional, non-functional and interface requirements. 4. Appendices Index Adapting the standard The IEEE standard is a generic standard which is intended apply to a wide range of requirements documents. In general, not all parts of the standard are required for all requirements documents Each organisation should adapt the standard depending on the type of systems it develops Consider a company (XYZ) that develops scientific instruments Organisation XYZ standard Preface This should define the expected readership of the document and describe its version history including a rationale for the creation of a new version and a summary of the changes made in each version. Introduction This should define the product in which the software is embedded, its expected usage and present and overview of the functionality of the control software. Glossary This should define all technical terms and abbreviations used in the document. Organisation XYZ standard General user requirements This should define the system requirements from the perspective of the user of the system. These should be presented using a mixture of natural language and diagrams. System architecture This chapter should present a high-level overview of the anticipated system architecture showing the distribution of functions across system modules. . | Lecture 5 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science 1 Requirements document structure IEEE/ANSI 830-1993 standard proposes a structure for software requirements documents 1. Introduction 1.1 Purpose of requirements document 1.2 Scope of the product 1.3 Definitions, acronyms and abbreviations 1.4 References 1.5 Overview of the remainder of the document Requirements document structure 2. General description 2.1 Product perspective 2.2 Product functions 2.3 User characteristics 2.4 General constraints 2.5 Assumptions and dependencies 3. Specific requirements Covering functional, non-functional and interface requirements. 4. Appendices Index Adapting the standard The IEEE standard is a generic standard which is intended apply to a wide range of requirements documents. In general, not all parts of the standard are required for all requirements documents Each organisation should adapt the .