Perancangan Basis Data Gathering Business and System Requirements

What is Requirements? • Menurut IEEE Standard Glossary of Software Engineering Technology : 1. Suatu kondisi atau kemampuan yang diperlukan oleh user untuk memecahkan masalah atau mencapai tujuan. 2. Suatu kondisi atau kemampuan yang harus dipenuhi atau dimiliki oleh sistem atau komponen sistem untuk memenuhi kontrak, standard, spesifikasi atau dokumen formal lain. 9/26/2020 2

What is Requirements? • Menurut Sommerville [SOMM] : Spesifikasi dari apa yang harus diimplementasikan, deskripsi bagaimana sistem harusnya berkerja atau bagian-bagian yang ada didalam sistem, bisa juga dijadikan batasan dalam proses pengembangan sistem. 9/26/2020 3

What is Requirements? • The term is important to note, developers requirement, must be able to distinguish the term shall, will, and should. • Shall => Requirement • Will => Statement of facts • Should => The Goal 9/26/2020 4

What is Requirements? Requirements are usually written in the form : • The System shall provide …… • The System shall be capable of … • The Subsystem #1 shall provide 9/26/2020 5

Gathering Business and System Requirements • • Types of Requirements Overview of Requirements Analysis Determining Business Requirements Analyzing Business Requirements Determining System Requirements Determining the Direction of Database Design Preliminary Documentation Evaluating Analysis 9/26/2020 6

Types of Requirements 9/26/2020 7

Types of Requirements (General) • In general, Two types of requirements: 1. Functional requirement describes the functional of the system. 2. Non-Functional requirement whose role is to impose limits on the solutions or so-called quality requirement. 9/26/2020 8

Types of Requirements • Two types of requirements are used to design an information system (Ryan K. Stephens and Ronald R. Plew): 1. Business requirements refer to those details that are related to how a business functions on a daily basis. 2. System requirements are those details, many of which are associated with business requirements, that are used to actually design the system. 9/26/2020 9

Types of Requirements Business requirements • • • Who will perform the tasks? How are tasks performed? How do the processes interact with one another? How do the organizational units interact with one another? What outside factors exist that affect business processes and data? 9/26/2020 10

Types of Requirements System requirements • • Which processes are the most critical? Will all organizational units share the same system? Will information be gathered from an existing system? Who are the users of the new system? 9/26/2020 11

Overview of Requirements Analysis 9/26/2020 12

Overview of Requirements Analysis • Requirements analysis is the process of analyzing the business and system requirements that have been established. • Requirements analysis is a sort of evaluation of the work that took place during the analysis phase (information gathering). • The customer should verify that all needs of the business have been considered, as the end user should verify that the needs of the information system have been properly converted from the needs of the business. 9/26/2020 13

Determining Business Requirements 9/26/2020 14

Determining Business Requirements The preliminary steps : 1. Research of the business is conducted. a research study should be conducted of the business so that the interviewers understand what types of questions to ask the individuals being interviewed. Performing research ahead of time will allow the development team to be more organized when compiling interview questionnaires and will save more time during the actual interview process. 2. An interview plan is established. The interview plan can include topics such as the individuals to be interviewed, the individuals conducting the interviews, cross interviews, and end-user feedback sessions throughout the design process. 3. A template is created with basic questions that trigger more specific questions. The template should have very basic questions that will be used to trigger more specific questions. 9/26/2020 15

Determining Business Requirements Who ? ? • The primary informational resources for requirements gathering include the following: The customer, The end user, and Management. • Scenario : 1. Interviewing Management 2. Interviewing the Customer 3. Interviewing the End User 4. Studying the Existing Processes in Place 9/26/2020 16

Determining Business Requirements Interviewing Management • Following are some important questions that should be directed to management during the interviews: 1. 2. 3. 4. 9/26/2020 From your perspective, what are the goals of the business? How will the database affect management? How is data transmitted between departments? What is management’s expectations of the system? , dll. 17

Determining Business Requirements Interviewing the Customer • The following questions should be directed to the customer in regards to the daily functions performed: 1. 2. 3. 4. 9/26/2020 What services or products do you provide? Are activities manual or automated processes? What problems exist with current automated processes? What is the expected outcome of each business process? , dll. 18

Determining Business Requirements Interviewing the Customer • The following questions should be directed to the customer with regard to the data: 1. 2. 3. 4. 9/26/2020 What is the data? Who uses the data? How long must the data be kept? How much data do you have? , dll. 19

Determining Business Requirements Interviewing the End User • The following questions should be directed to the end user with regard to the daily functions performed by the user: 1. 2. 3. 4. 9/26/2020 What is your primary job function? What else do you do? How do you do it? What tools are currently used to perform your job? , dll. 20

Determining Business Requirements Studying the Existing Processes in Place • Following are considerations for evaluating existing processes : 1. 2. 3. 4. How are business transactions currently handled? What is the goal of each process? Are the goals currently being met? What processes can be automated that are not already? , dll. 9/26/2020 21

Analyzing Business Requirements 9/26/2020 22

Analyzing Business Requirements The analysis should outline the following information : • • • Interview details Personnel and time resources required Review of the legacy system Deliverables (diagrams) Tasks assigned and to whom Dates and deliverables for user feedback sessions 9/26/2020 23

Analyzing Business Requirements Following are some of the most common diagrams used to analyze business requirements : • Entity relationship diagrams (ERDs)—Define the data and show relationships between data. • Process Models—Show process steps involved in each process • Data flow diagrams—Show data moves through an organization, from processes to data stores • Function hierarchy diagrams—Show processes are related to one another 9/26/2020 24

Analyzing Business Requirements User Feedback • Let the customer see your perception of the business. • The best way to ensure a successful design is to have the end users’ and customer’s stamp of approval on each deliverable of the design process that pertains to the completeness of the database. 9/26/2020 25

Determining System Requirements 9/26/2020 26

Determining System Requirements • The conversion of business requirements into system requirements involves the following steps: 1. 2. 3. 4. 9/26/2020 Identifying the data Grouping the data that has been defined Establishing a list of fields Establishing data relationships 27

Determining System Requirements Identifying the data • A significant part of the interview process includes the identification of business data. • Data will be found throughout the notes taken during the interviews. 9/26/2020 28

Determining System Requirements Grouping the data that has been defined • Examples of basic groups of data for an online bookstore might include : q Book information q Author information q Publisher information q Distributor information q Order information, dll. 9/26/2020 29

Determining System Requirements Establishing a list of fields • In association with book information, an online book store might require the following information: q Book ISBN q Book title q Description q Category q Publisher q Author q Publication date q Cost 9/26/2020 30

Determining System Requirements Establishing data relationships • Relationships allow one or more entities to be related. • For example, consider the following entities and brief lists of fields: Product inventory (Book information, Author information, stock) 9/26/2020 31

Determining the Direction of Database Design 9/26/2020 32

Determining the Direction of Database Design The steps involved : • • Database model to be used Implementation to be used Establishment of naming conventions and standards Establishment of milestones and deliverables 9/26/2020 33

Determining the Direction of Database Design Determining the Type of Database Model • In most cases in today’s world, the choice will be the relational database model. • The model that best suits the needs of the business must be selected 9/26/2020 34

Determining the Direction of Database Design Selecting an Implementation • If the relational database model is being used, a relational database management system (RDBMS) must be selected. • Some common relational database management systems include : q Oracle q Microsoft SQL Server q Microsoft Access q My. SQL 9/26/2020 35

Determining the Direction of Database Design Setting Naming Conventions and Standards to Be Used • How will entities be named? • How will attributes be named? • How will tables be named? • How will columns be named? 9/26/2020 36

Determining the Direction of Database Design Setting Milestones and Deadlines • Sample major milestones for a database design effort: 1. Design team is formed. 2. Project kick-off meeting is conducted. 3. Strategy plan is devised. 4. Interview plan is devised. 5. Interviews are conducted. 6. Lists of fields established. 7. Initial ERD is built. 8. Process models, data flow models, and function hierarchy diagrams are drawn. 9. User feedback sessions are conducted. 10. Detailed ERD is built. 11. User feedback sessions are conducted. 9/26/2020 37

Determining the Direction of Database Design Setting Milestones 12. Cross-check ERD with processes is created. 13. User feedback sessions are conducted. 14. Design of the physical model begins. 15. Further normalization of the physical model occurs. 16. Views are designed. 17. The database is generated. 18. The database is tested with the user application. 19. Production implementation occurs. 9/26/2020 38

Preliminary Documentation 9/26/2020 39

Preliminary Documentation involved in the information gathering stage of database design includes : • A high-level work plan • A strategy document • A detailed requirements document 9/26/2020 40

Preliminary Documentation A high-level work plan • This plan should include : q The major steps projected to design the database q The major tasks that will be involved during design q Identification of major milestones q Identification of major deliverables q Outline of the resources required for the project q Estimate of the personnel required for the project q Estimate of the desired time frame to completion of the project 9/26/2020 41

Preliminary Documentation A Strategy Document • Business requirements are the data, processes, and rules that comprise a business. • Diagrams that should be included in the strategy document are : q High-level entity relationship diagrams (entities and relationships only) q High-level business process models (main processes only) 9/26/2020 42

Preliminary Documentation A Detailed Requirements Document • The detailed requirements document should include : q A detailed listing of database requirements that pertains to all appropriate organizational units within the organization q All available legacy database documentation that pertains to the new database q Business goals q Outline of all design phases, milestones, and deliverables q Objectives for each design phase q The business rules as gathered from interviews (many business rules reflected in diagrams) q Detailed diagrams as drawn during requirements analysis 9/26/2020 43

Preliminary Documentation A Detailed Requirements Document • Diagrams that should be included in the requirements document are: q Detailed entity relationship diagrams q Detailed business process models q Hierarchy of business processes q Data flow diagrams 9/26/2020 44

Evaluating Analysis 9/26/2020 45

Evaluating Analysis • The following considerations should be taken to measure the completeness of information gathering and requirements analysis: q Have all steps been followed so far? q Is the direction of design still within the scope of the mission statement and objectives? q Have all requirements been gathered in order to design a database? q Is the Entity Relationship Diagram (ERD) correct? q Is the function hierarchy correct? q Do the requirements make sense to the development team? q Were all deliverables acceptable to customer, end user, and management? q Were all objectives of requirements analysis met? 9/26/2020 46

Semua materi bisa di download di akademik. neoticsolusindo. com cek menu Course 9/26/2020 47