Sem

Published on November 2016 | Categories: Documents | Downloads: 45 | Comments: 0 | Views: 470
of 25
Download PDF   Embed   Report

Comments

Content

Module Name: Software Engineering Method

Submitted By Zahid Masum Ncc Id Center

Page | 1

Table of contents
Introduction ------------------------------------------------------------------------------------------------------------- 3 Task 1 1.1 1.2 Task 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 9 Event list for the Riverside Archive Management system ----------------------------------------Context DFD of the system ERD of the system 9 -----------------------------------------------------------------------JAD (Joint Application Design) ---------------------------------------------------------------Role of JAD workshops in DSDM ---------------------------------------------------------4 4

------------------------------------------------------------------------------ 10 11 --------------------------------------------------------------

The „middle level‟ DFD fragments

Lower level DFDs for 'Reserve a document‟ and „List reserved documents'. ------- 15 Data Dictionary ------------------------------------------------------------------------------ 17

Pspecs for elementary processes „belonging‟ to 'Reserve a document' and 18 'List reserved documents' ------------

Task 3 3.1 3.2 3.3 Structure chart (upper level) for the whole system ---------------------------------------- 20

21 Structure charts for 'Reserve a document', and 'List reserved documents' ------------Mspecs for all 'Reserve a document' modules 23 -------------------------------------------

Summary

-------------------------------------------------------------------------------------------------------------- 24

Bibliography ------------------------------------------------------------------------------------------------------------- 25

Page | 2

Introduction

Page | 3

Task 1
Questions of Task 1
• Write a brief section (one page) in which you explain JAD (Joint Application Design) • Discuss the role of JAD workshops in DSDM (i.e. how and where in DSDM they can be used)

JAD (Joint Application Design)

JAD stands for Joint Application Design which is used for collecting user requirements and creating system designs for constructing professional software. It defines list of user requirements presenting prototype system. It is also a requirement approach to build quality software and meet customer expectation. This approach involved users, managers and system analysts. This requirement processes are reviewed in structured meetings. JAD-like techniques are fitting gradually more common in systems planning and analysis to acquire group agreement on problems, objectives, and requirements.

The role of JAD workshops in DSDM

Joint Application Design (JAD) is a procedure used in the prototyping life cycle area of the Dynamic Systems Development Method (DSDM) to gather business requirements at the same time as developing new systems for an organization company or customer. Doing JAD workshops the facts workers and IT specialists are capable to resolution any difficulties or differences between the parties concerning the new system. The workshop pursues a in depth agenda in order to undertaking that all suspicions between parties are enclosed and to help put off any miscommunications.

Page | 4

Joint application design participants Sponsor (top management, final say) Leader (facilitator, independent) Users and Managers (requirements, business rules) Scriber(s) IS staff Joint application design sessions Most JAD sessions span a three- to five-day time period and occasionally last up to two weeks. The success of any JAD session is dependent upon proper planning and effectively carrying out that plan. Planning the JAD sessions • Before planning a JAD session, the analyst and sponsor must determine the scope of the project. It is also important that the high-level requirements and expectations of each JAD session is determined. Ensure that the sponsor is willing to commit people, time, and other resources to effort. • Planning for a JAD session involves three steps: – – – Selecting location. Selecting participants. Preparing agenda.

Selecting participants Sponsor, analysts and managers select a leader. Leader may be in-house or contracted in one or more scribes must also be selected. Normally selected from the IS staff • • IS Staff are selected from the development team(s) Analyst and managers must select individuals from the user community. Should be knowledgeable about their business are and able to articulate it.

Page | 5

Conducting a JAD session • • Session begins with brief overview of agenda and objectives. Leader should follow these guidelines: – – – – – – – Stick to agenda. Stay on schedule (agenda topics are allotted specific time). Ensure scribe is able to take notes. Avoid technical jargon. Resolve conflicts (try not to defer). Encourage group consensus. Encourage user and management participation without allowing individuals to dominate the session. – Make sure that attendees abide by the established ground rules.

JAD document • The end product of a JAD session is typically a formal written document. – Essential in confirming the specifications agreed upon during the session(s) to all participants. – – Content and organization of specification obviously dependent on objectives of session. Analyst may choose to provide different set of specifications to different participants based upon their role.

Page | 6

Benefits of JAD • An effectively conducted JAD session offers the following benefits: – JAD actively involves users and management in the development project (encouraging them to take “ownership” in the project). – – JAD reduces the amount of time required to develop systems. When JAD incorporates prototyping as a means of confirming requirements and obtaining design approvals, benefits of prototyping are realized

Page | 7

Task 2
Questions of Task 2
Environmental model specification (Yourdon) • Event list for the system • Context DFD Internal model specification (Yourdon) • ERD for the system • The „middle level‟ DFD fragments • Lower level DFDs for the following „functions‟: 'Reserve a document‟ and 'List reserved documents'. • Data Dictionary (with definitions of major data flows and definitions of entities) • Process specifications (Pspecs) for elementary processes „belonging‟ to 'Reserve a document', and 'List reserved documents'. (i.e. how and where in DSDM they can be used)

Page | 8

Event list for Riverside Archive Document Library Management System

      

Add document records Delete document records Borrow a document Return document Document reservation Reader registration Deregister inactive readers Show document reservation detail



Context DFD

Figure 2.2: Context DFD of the Riverside Archive Document Library Management System

Page | 9

ERD for the system

Figure 2.3: ERD of the Riverside Archive Document Library Management System

Page | 10

The ‘middle level’ DFD fragments

Figure 2.4.1: Middle Level DFD Fragment for „Add Document‟

Figure 2.4.2: Middle Level DFD Fragment for „Delete Document‟

Page | 11

Figure 2.4.3: Middle Level DFD Fragment for „Borrow Document‟

Figure 2.4.4: Middle Level DFD Fragment for „Return Document‟ Page | 12

Figure 2.4.5: Middle Level DFD Fragment for „Reserve Document‟

Figure 2.4.6: Middle Level DFD Fragment for „Register new Reader‟

Page | 13

Figure 2.4.7: Middle Level DFD Fragment for „De-register 12 months inactive Readers‟

Figure 2.4.8: Middle Level DFD Fragment for „List Reserved Documents‟

Page | 14

Lower level DFDs for the functions 'Reserve a document’

Figure 2.5.1: Lower Level DFD for „Reserve a Document‟

Page | 15

Lower level DFDs for the functions 'List reserved documents’

Figure 2.5.2: Middle Level DFD Fragment for „List reserved Documents‟

Page | 16

Data Dictionary

Document = { Document }

/* data store

Document_details= Doc_code + Date_of_registration + Date_of_last_loan + Summary + Password + subject Reader = { Reader } /* data store

Reader_details= Reader_no + Reader_name + Date_of_registration + Date_of_lastloan Borrow_Records = { Borrow_Records } /* data store Borrow_details = Reader_no + Doc_code + Date Reservation_Records = { Reservation_Records } /* data store Reservation_details = Doc_code + Date + Reader_no List_reserved_documents = Reservation_Records + Reservation_details

Page | 17

Process specifications (Pspecs) for elementary processes ‘belonging’ to 'Reserve a document'
Get Reader_no Get Doc_code While Reservation_Data.Doc_code = Doc_code { Read Date from Reservation Data Display Date } Get Date While Reservation_Data.Doc_code = Doc_code { Read Date from Reservation Data If(Reservation Data.Date = Date) { Display Error END Process } } validData = Reader_no, Doc_code, Date Display Reservation CONFIRMATION

Page | 18

Process specifications (Pspecs) for elementary processes ‘belonging’ to 'List reserved documents'

While more Reservation_Data { Read Date from Reservation Data Read Doc_code from Reservation Data Read Reader_no from Reservation Data

Read Reader_name from Reader

validDetail = Doc_code, Reader_no, Date Display validDetail

}

Page | 19

Task 3
Questions of Task 3

Design specification (Yourdon) • Structure chart (upper level) for the whole system • Structure charts for 'Reserve a document', and 'List reserved documents'. • Module specifications (Mspecs) for all 'Reserve a document' modules (i.e. modules contributing to this function).

Structure chart (upper level) for the whole system

Figure 3.1: Structure Chart (Upper level)

Page | 20

Structure chart for 'Reserve a document'

Figure 3.2.1: Structure Chart for „Reserve a Document‟

Page | 21

Structure chart for 'List reserved documents'

Figure 3.2.2: Structure Chart for „List reserved documents‟

Page | 22

Module specifications (Mspecs) for all 'Reserve a document' modules
MODULE NAME: „Reserve a document‟ PURPOSE: This module is used to allow a valid reader to reserve a document on a particular date when the document is available (i.e. not reserved by any other) PSEUDOCODE: Get Reader_no Get Doc_code While Reservation_Data.Doc_code = Doc_code { Read Date from Reservation Data Display Date } Get Date While Reservation_Data.Doc_code = Doc_code { Read Date from Reservation Data If (Reservation_Data.Date = Date) { Display Error END Process } } ValidData = Reader_no, Doc_code, Date Display Reservation CONFIRMATION INPUT PARAMETERS OUTPUT PARAMETERS GLOBAL VARIABLES LOCAL VARIABLES CALLS CALLED BY : Reader_no, Doc_code, Date : validData : None : Date, Reader_no, Doc_code : „List reserved documents‟ : System

Page | 23

Summary

This assignment consist of three main tasks covering JAD sessions & DSDM, Environmental & Internal model specification (Yourdon) and Design specification (Yourdon). First task of this assignment is to describe JAD sessions and DSDM. Second task is to implement Yourdon‟s Environmental model specification and internal model specification based on a given scenario of Riverside Archive Document Library. The third task is to implement Yourdon‟s Design Specification based on a given scenario of Riverside Archive Document Library.

Page | 24

Bibliography

Page | 25

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close