system development methods
DESCRIPTION
Assignment done at APIIT Lanka for the module System Development MethodsTRANSCRIPT
ASIA PACIFIC INSTITUTE OF INFORMATION
TECHNOLOGY
INCOURSE ASSIGNMENT
SYSTEM DEVELOPMENT METHODS
Prepared By
A.N.Ahamed Nishadh (CB004081)
S.D.Ilangakoon (CB004041)
M.J.Dilshan Zuhdi (CB004050)
Module Code & Title
CE00321-2-SDM
Cohort
HF11B1SE
Date of Submission
8th February 2012
Instructor
Ms.Nadeera Ahangama
Submitted in partial fulfillment for the degree of
Bachelor of Science (Hons) in Computing
i
ACKNOWLEDGEMENTS
Firstly we would like to thank our lecturer Ms.Nadeera Ahangama for all the help
and guidance given while doing this assignment.
Also there are many individuals who have helped us in numerous ways directly
and indirectly so that we were able to complete this assignment.
APIIT Lanka for providing us with resources and the Tech Team at APIIT Lanka
for their assistance at required times.
And last but not least our friends, parents and the well-wishers without whose
moral support and encouragement, we would not have been able to do a good job.
Finally, if there are any shortcomings in this project, then we request to excuse us
for all those and accept this documentation.
Ahamed Nishadh
Deshan Ilangakoon
Dilshan Zuhdi
ii
WORKLOAD MATRIX
Task Ahamed
Deshan Dilshan
Introduction
Schedule Planning
Gantt Chart
Selection of Methodology
Problem Analysis – Current
System
Overview – Proposed System
Process Modeling
Context Diagram
Level 0 DFD
Level 1 DFD
Data Modeling
ER Diagram
Event Modelling
Entity Life History
Data Dictionary
Data Flows
Data Stores
Processes
External Entities
Database Development
Interactive Screen Designs
Report Designs
Programming Environment
Implementation of Prototype
Documentation
100
0
0
0
25
33
33
33
60
0
33
33
33
33
100
50
25
50
0
33
0
100
0
100
50
33
33
33
20
0
33
33
33
33
0
25
25
50
0
33
0
0
100
0
25
33
33
33
20
100
33
33
33
33
0
25
50
0
100
33
iii
GANTT CHART
A3 PAGE COMES HERE!!!
iv
TABLE OF CONTENTS
1.0 - INTRODUCTION ............................................................................................... 1
2.0 – ASSUMPTIONS ................................................................................................. 2
3.0 – SELECTION OF METHODOLOGY ................................................................. 3
3.1 - STRUCTURED SYSTEM ANALYSIS AND DESIGN
METHODOLOGY (SSADM) ............................................................................. 3
3.1.1 – MAIN OBJECTIVES OF SSADM ...................................................... 3
3.1.2 – MAIN STAGES OF SSADM METHODOLOGY .............................. 4
3.1.3 – ADVANTAGES OF SSADM.............................................................. 4
3.1.4 – DISADVANTAGES OF SSADM ....................................................... 5
3.2 – IMPLEMENTATION STRATEGIES ........................................................ 5
4.0 – PROBLEM ANALYSIS OF CURRENT SYSTEM ........................................... 6
5.0 – OVERVIEW OF THE PROPOSED SYSTEM ................................................... 7
5.1 – FUNCTIONAL SPECIFICATIONS .......................................................... 7
5.1.1 – MANAGING FRONT OFFICE ........................................................... 7
5.1.2 – MANAGING OF EVENTS ................................................................. 8
5.1.3 – PROCUREMENT AND INVENTOR MANAGEMENT ................... 8
5.1.4 – PAYMENT MANAGEMENT ............................................................ 8
5.1.5 – MANAGING EMPLOYEES ............................................................... 8
5.1.6 – MONITORING REPORTS ................................................................. 9
5.2 – NON – FUNCTIONAL SPECIFICATIONS ........................................... 10
v
6.0 – DATA FLOW DIAGRAMS ............................................................................. 11
6.1 – CONTEXT DIAGRAM ............................................................................ 11
6.2 – LEVEL 0 ................................................................................................... 12
6.3 – LEVEL 1 OF PROCESS 2 ....................................................................... 13
6.4 – LEVEL 1 OF PROCESS 3 ....................................................................... 14
6.5 – LEVEL 1 OF PROCESS 4 ....................................................................... 15
6.6 – LEVEL 1 OF PROCESS 5 ....................................................................... 16
6.7 – LEVEL 1 OF PROCESS 6 ....................................................................... 17
6.8 – LEVEL 1 OF PROCESS 7 ....................................................................... 18
7.0 - ENTITY RELATIONSHIP DIAGRAM ........................................................... 19
8.0 – DATA DICTIONARY ...................................................................................... 20
8.1 – DATA STORES ....................................................................................... 20
8.2 – DATA FLOWS ......................................................................................... 24
8.3 – EXTERNAL ENTITIES ........................................................................... 42
8.4 – PROCESSES ............................................................................................ 44
9.0 – ENTITY LIFE HISTORY ................................................................................. 51
9.1 – CUSTOMER ENTITY ............................................................................. 51
9.2 – ORDERS ENTITY ................................................................................... 52
9.3 – EMPLOYEES ENTITY ........................................................................... 53
9.4 – INVOICE ENTITY .................................................................................. 54
9.5 – INVENTORY ENTITY ............................................................................ 55
vi
9.6 – SUPPLIER ENTITY ................................................................................ 56
9.7 – SUBTASKS ENTITY .............................................................................. 57
10.0 – SCREEN DESIGNS ........................................................................................ 58
10.1 – ADD NEW CUSTOMER ....................................................................... 58
10.2 – ADD NEW EMPLOYEE ....................................................................... 59
10.3 – ADD INVENTORY ITEM ..................................................................... 60
10.4 – ADD NEW ORDER ............................................................................... 61
10. 5 – SEARCH / MODIFY ORDER .............................................................. 62
10.6 – ADD NEW SUBTASK .......................................................................... 63
10.7 – ADD EMPLOYEES TO SUBTASK ...................................................... 64
10.8 – ADD INVENTORY ITEMS TO SUBTASK ......................................... 66
10.9 – ADD 3RD
PARTY SUPPLIER TO SUBTASK ...................................... 68
10.10 – ADD NEW 3RD
PARTY SUPPLIER ................................................... 70
10.11 – ADD 3RD
PARTY SUPPLIER PRODUCTS / SERVICES.................. 71
10.12 – MODIFY CUSTOMER DETAILS ...................................................... 72
10.13 – MODIFY EMPLOYEE DETAILS ....................................................... 73
10.14 – MODIFY SUPPLIER DETAILS ......................................................... 74
10.15 – MODIFY 3RD
PARTY SUPPLIER PRODUCT / SERVICE DETAILS
........................................................................................................................... 75
10.16 – RETURN INVENTORY ITEM ........................................................... 76
10.17 – LOAD INVOICE .................................................................................. 77
10.18 – INVOICE .............................................................................................. 78
vii
10.19 – LOGIN .................................................................................................. 79
10.20 – MAIN MENU ....................................................................................... 80
11.0 – REPORT DESIGNS ........................................................................................ 81
11.1 – PROFIT / LOSS REPORT ..................................................................... 81
11.2 – REPORT ON SUPPLIERS AND PRODUCTS / SERVICES THEY
PROVIDE .......................................................................................................... 82
11.3 – REPORT ON STAFF ALLOCATED PER EVENT .............................. 83
11.4 – EVENTS ON A PARTICULAR MONTH ............................................. 84
11.5 – INVOICE ................................................................................................ 85
12.0 – DEVELOPMENT ENVIRONMENT ............................................................. 86
12.1 – LANGUAGE OF PROGRAMMING ..................................................... 86
12.2 – PROGRAMMING TOOLS .................................................................... 86
12. 3 – DATABASE .......................................................................................... 86
13.0 – BIBLIOGRAPHY ........................................................................................... 87
1
1.0 - INTRODUCTION
In this project of ours, we have been given the task of making a system for an
event management company named Planit Event Management (Pvt) Ltd. The
management of the company has decided to invest in a new information
management system so that they can automate their office processes for work to
be done faster and efficiently.
There are different areas of the company that are going to be combined and
automated using thing system. The front office, the human resource office, the
stores where the inventory is kept, the accounts department and the management
are all going to be connected using this system.
The prototype system we are designing would be done using C#.net and we would
be using the SSADM methodology to develop the system and implement it.
The system would be mainly used by the staff and management of the company
only. No external personal would be using the system as it is an internal
information management system and allowing access to external people would
compromise the security of the system.
The system would handle all the inquiries by the customers, direct them to the
relevant officials, help in managing the events that the company is doing, help in
inventory management, payment process and create necessary reports for
management.
2
2.0 – ASSUMPTIONS
In this project, we have taken certain assumptions on how the processes work
manually and have implemented the same in the automated system. They are as
follows.
1. Each event managed by the company will be headed by one person called
the Event Manager who will have full control over everything that
happens in that particular event.
2. When a client makes an inquiry, depending on the type of inquiry
(consultation, event organizing, itinerary management etc.) the quotation
would take at least 24-72 hours to be prepared and sent to the customer.
3. If the company does not have adequate staff or do not have staff of a
particular type or do not provide a particular service in house (catering,
magicians for kids parties, security personal for events, etc.), they will be
obtaining the services of 3rd
party suppliers but all these will be going
through the company and not as external partners for the event.
4. At least 50% of the payment of the quoted amount has to be made prior to
the event and the balance depending on the final amount will have to be
settled after the event by the client.
5. The quotation would provide an estimated amount for the requirements of
the client while the final cost would change according to the changes in
plans and costs of the customers’ requirements while the event is being
planned.
6.
3
3.0 – SELECTION OF METHODOLOGY
A good software project is the result of a proper structured development
methodology followed by all those involved in the project. Hence, we too decided
to use a recognized development methodology to handle our project. The
methodology we decided to use was the Structured System Analysis and Design
Methodology (SSADM).
3.1 - STRUCTURED SYSTEM ANALYSIS AND DESIGN
METHODOLOGY (SSADM)
SSADM was developed in the year 1980. It’s the standard design of information
systems in the United Kingdom. It breaks up a development project into stages,
modules, steps and tasks. The first model developed in SSADM is the data model.
The techniques used in SSADM are as follows.
1. Data Flow Modeling - It involves in data flow tracking in an information
system. This analyzes the data stores, process, external entities and data
movement clearly.
2. Logical Data Modeling - This engages with process identifying,
modeling and documenting data as a part of system requirement gathering.
And then data are classified further into relationships and entities.
3. Entity Behavior Modeling - This engages in identifying and
documenting the events influencing each entity and the sequence in which
these events happen.
3.1.1 – MAIN OBJECTIVES OF SSADM
1. Develop better and high quality systems.
2. Good communication between participants in a project by establishing a
framework.
3. Make projects resilient to the loss of staff.
4. Improve the project management and control.
4
5. Make use of experienced and inexperienced development staff more
effectively.
6. Allows projects to be supported by computer based tools as computer
aided software engineering systems.
3.1.2 – MAIN STAGES OF SSADM METHODOLOGY
1. Feasibility Study: It covers a large level analysis of business area to
conform whether the particular system is feasible to develop.
2. Requirement Analysis: In this stage, requirements are identified and
current business environment is modeled, business system options are
produced and presented. From these, one is chosen and refined. The
possible techniques that are used in this stage are Logical Data Modeling
and Data Flow Modeling.
3. Requirement Specification: In this stage functional and non-functional
requirements are specified as a result of the requirement analysis stage.
Data Flow Modeling, Entity Event Modeling and Logical Data Modeling
can be used as techniques.
4. Logical System Specification: In this stage implementation and
development environment are specified. The logical design of update and
enquiry processing and system dialogs are carried out.
5. Physical Design: In this technical specification and the logical design are
used to create physical design and set program specification.
It should be noted that in the SSADM methodology, Implementation and
Maintenance of the developed system are not part of the stages. Hence we will be
using the Traditional Software Implementation Methodology about which we
have specified in this documentation below.
3.1.3 – ADVANTAGES OF SSADM
1. It offers better understanding.
2. It’s highly practical.
3. Coherent design.
4. High Quality system is delivered at the end of project.
5
3.1.4 – DISADVANTAGES OF SSADM
1. It has a long development times because every stage must be completed
before moving on to the next stage.
2. It costs time and money, Organizations must have large resources.
3. Lack of user involvement.
4. It’s not flexible.
3.2 – IMPLEMENTATION STRATEGIES
We are developing a prototype of our system. Prototype is building process of a
system. It’s a repeating process which is a part of analysis phase of system
development life cycle. In the initial stage of analysis some uses papers to get user
feedbacks and later on develop a prototype using fourth generation languages like
visual basic during the design stage.
There are many forms of prototyping -From low tech sketches or paper screens,
which users and developers can paste controls and objects. To high tech
operational systems CASE(computer aided software engineering).
There are many Advantages of Prototyping
It requires user involvement
It results in high user satisfactions.
It reduces development costs.
It reduces development time.
And there are some disadvantages also
Developers may become too attached to their prototypes.
It sometimes guide to incomplete documentation.
It can guide to insufficient analysis.
6
4.0 – PROBLEM ANALYSIS OF CURRENT SYSTEM
PLANIT Event Management (Pvt) Ltd is a large and successful event planning
company that has decided to invest in a new information management system.
This system is to allow for better information management. The following
problems have been noted in the current existing system.
1. The system currently maintains all its records manually I hardcopy form
and none of the process is automated at all. This leads to slower and a lot
of wasted resources in attempting to maintain the system and in trying to
keep all the records up to date.
2. There is a great risk of information being misused by people who should
not be allowed to view it. This problem is slightly improved by keeping all
the records in storage closets with locks. This feature can be easily
breached and also careless oversight on the part of the employee where
records re forgotten to be locked up after use.
3. Threat of records being destroyed easily. Since all records are maintained
in hardcopy format there is a really great possibility of the information
being ruined by factors beyond human control like water damage and the
possibility of harmful products accidently falling on to the records. The
possibility also exists that an external party may remove pages from the
legers containing the information.
4. Another threat faced by the current system is the threat of incorrect
information being entered into the system by accident. This is a great
threat as its only human to make mistakes and taking into consideration
the large amount of information passing through the company, it is
possible that a mistake might go unnoticed until it’s too late to correct it or
the damage is permanent. This will add to additional costs to the company
when it tries to rectify its errors.
7
5.0 – OVERVIEW OF THE PROPOSED SYSTEM
5.1 – FUNCTIONAL SPECIFICATIONS
Our team has been asked to develop a system for PLANIT Event Management
(Pvt) Ltd, Colombo. The system that has been requested is an information
management system. This system has several primal requirements that have been
requested for by the Management of PLANIT.
The Basic Requirements are as follow:
1. Manage Front Office
2. Managing of Events
3. Procurement and inventor Management
4. Payment Management
5. Managing of Employees
6. Monitoring Reports
In developing the new system our team took extreme care to ensure that the above
mentioned five basic requirements are met exactly as the client had requested.
5.1.1 – MANAGING FRONT OFFICE
This is where the customer of the company will make his initial request for
assistance in organizing the event. The front desk will be the point of contact for
the customer with the company. Here there are several processes that can be
carried out.
Registration of the customer – This will be the initial step. The customer
will provide all the required information to the front office and this
information will be saved in the company records.
Reservation – Here the customer will provide all the details of the event
and this information will be cross checked against the availability and the
customer will be told if the company is able to cater to the request.
8
Cancelation – In the event that the customer wishes to cancel his or her
event the customer will again inform the front office and the front office
will cancel the event and the appropriate charges will be applied.
5.1.2 – MANAGING OF EVENTS
The management of the events is a vital part in this organization. It mainly
will deal with customer in the event that the customer wishes to change
retails regarding the event.
The allocation of the event planner or the event manager will also be done
here. The system will check its records and allocate the most suited and
available planner to an event wen the customer makes the request.
5.1.3 – PROCUREMENT AND INVENTOR MANAGEMENT
This segment of the system will deal with the handling of the companies supplies
and the resources that will be outsourced. The system will check within itself for
records of the utilization of the company’s products and inform the system user if
the company has enough equipment on its own to provide for the event.
Procurement of supplies from outside dealer will also be done in the event that the
company does not have the required resources or when the company has depleted
its own resources.
5.1.4 – PAYMENT MANAGEMENT
The payments due for handling the event will also be provided to the customer at
this point. The customer will receive an invoice to which they are then expected
to provide the relevant payments.
Further the customer will provide information such as the method of payment and
the payment scheme. At the payment point the customer will also be given
information such as if he will be receiving a discount.
5.1.5 – MANAGING EMPLOYEES
For a successful event to be organized the key requirement is proper management
of resources. Staff is one such vital resource and the management and the
9
allocation of the staff for the events will be carried out from this point of the
system.
New employees can be added and existing employee information can be changed
or permanently removed.
5.1.6 – MONITORING REPORTS
The reports will be generated by the system as a method of overseeing the work
that has been happening throughout the company. This information will only be
available to the administrative staff of the company and the management.
There will be five different reports generated by the system for the use of the
management.
1. Monthly and Annual Reservation Reports
2. Low Supplies Report and Free Supplies Report
3. Staff event Report
4. Income and Expenditure Report and Profit and Loss Report
5. Cancelation Report
Each of these will be generated by the system and presented to the administrative
user. This way the administration of the company can keep a close watch on all
the activities in the company and make changes as and when the situation
demands it.
10
5.2 – NON – FUNCTIONAL SPECIFICATIONS
The user of the new system has requested for several non-functional
specifications to be present in the system that is being developed.
Performance – The system will have to be able to perform all of its tasks
fast and efficiently. One of the main reasons for incorporating the new
system was in order that the time spent on manual processing of the
information received can be cut down. The system will also have to be
user friendly so that the user of the system will not find the using of this
system more tedious that the manual maintenance of the same system.
Security – This was a major concern for the senior management of the
company as the previous system’s lack of security. The system was unable
to effectively safeguard the information of its clients and the details of the
events and other sensitive information. Therefore this system will
incorporate several levers of access granting people access to only what
information they have the right to view. Other people without access will
therefore be safely prevented from viewing the system.
Reliability – It is vital for the system to be reliable. It should not fail at
critical points and that checking mechanisms be implemented to prevent
the entry of wrong data as much as possible. This is done with validation
checks and other such features. Though this will not completely prevent
wrong details from accidently being entered it will prevent information of
the wrong format to be entered.
Usability - For an effective system to be developed the system will also be
usable and flexible for change. During the development of the system our
team has tried as much as possible to make the system flexible for future
change.
11
6.0 – DATA FLOW DIAGRAMS
6.1 – CONTEXT DIAGRAM
12
6.2 – LEVEL 0
A3 PAGE COMES HERE
13
6.3 – LEVEL 1 OF PROCESS 2
14
6.4 – LEVEL 1 OF PROCESS 3
15
6.5 – LEVEL 1 OF PROCESS 4
16
6.6 – LEVEL 1 OF PROCESS 5
17
6.7 – LEVEL 1 OF PROCESS 6
18
6.8 – LEVEL 1 OF PROCESS 7
19
7.0 - ENTITY RELATIONSHIP DIAGRAM
A3 PAGE Comes here!!!
20
8.0 – DATA DICTIONARY
8.1 – DATA STORES
Name Customer File
Description Contains all the information regarding the clients of the
company who have made reservations with the company.
Input Data
Flows
Customer details
Output Data
Flows
N/A
Data Structure Customer File =
CustID+
CustName+
CustAddress+
CustTele+
CustRecStatus
Name Reservation File
Description Contains all the information reservations that the company
has and is to undertake in the future. This file is vital to make
sure that there are no events clashing with each other.
Input Data
Flows
Booking Details
Availability
Deleted Reservation Record
Output Data
Flows
Reservation Records
Data Structure Reservation File =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
21
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus
Name Inventory File
Description Contains details of all the supplies that the company holds.
The information in this file should always be up to date in
order that no accidental over booking of resources occur.
Input Data
Flows
Availability
Deallocated inventory records
Reserved inventory list
Output Data
Flows
Inventory Records
Data Structure Inventory File =
ItemID+
ItemName+
ItemDescription+
ItemSerialNumber+
ItemPrice+
ItemStatus+
ItemRecStatus+
DeptID
Name Staff File
Description Contains all the information regarding the company’s staff
and their availability or the current event that they are
22
engaged in. This information is valuable when checking to
assess if the company can cater to a client’s requirements.
Input Data
Flows
Availability
Allocated Staff List
Deallocated staff list
Output Data
Flows
Staff records
Data Structure Staff File =
EmpID+
EmpName+
EmpDoB+
EmpAddress+
EmpTele+
DeptID+
EmpDescription+
EmpStatus+
EmpRecStatus
Name Accounts File
Description This is another vital data store in that it contains all the
records of payments made and due. It also contains the
information regarding the quotations given to the clients so
that calculations can be made accordingly and accurately.
Input Data
Flows
Payment Details
Quotation
Invoice
Output Data
Flows
Accounts Details
Data Structure Accounts File =
InvID+
AccID+
InvPayMethod+
23
InvPayStatus+
InvPayable+
InvDiscount
Name Supplier File
Description This file will contain all the details of the products that a
supplier provides and also the details of the products that the
company has requested from the supplier.
Input Data
Flows
Cancel Product List
Supplier Details
Product Details
Output Data
Flows
N/A
Data Structure Supplier File=
SupID+
SupName+
SupAddress+
SupTel+
ProdName+
ProdType
24
8.2 – DATA FLOWS
Name Cancelation Information
Description Details regarding which event the Client wishes to cancel
Origin/Source Client External Entity
Destination Cancelation Process (6.1)
Data Structure Cancelation information =
CustID+
CustName+
OrdID+
OrdEventDate
Name Cancelation Reply
Description Sends the Client information regarding the possibility of
cancelling the event.
Origin/Source Cancelation Process (6.1)
Destination Client External Entity
Data Structure Cancelation Reply=
CustID+
CustName+
OrdID+
OrdEventDate+
OrdStatus
Name Deleted Reservation Record
Description Sends details of which record to be deleted from the
Reservation file
Origin/Source Cancelation Process (6.1)
Destination Reservation File
Data Structure Delete Reservation Record=
OrdID+
OrdStatus
25
Name Deallocated Staff Records
Description Sends details of which record to be deleted from the Staff file
Origin/Source Cancelation Process (6.1)
Destination Staff File
Data Structure Deallocate Staff Records=
OrdID+
EmpID+
OrdStatus
Name Deallocated Inventory Records
Description Sends details of which record to be deleted from the Inventory
file
Origin/Source Cancelation Process (6.1)
Destination Inventory File
Data Structure Deallocate Inventory Records=
OrdID+
STID+
ItemID+
OrdStatus
Name Cancelation Report
Description Sends the Administrator details of all the cancelled events
Origin/Source Report Process (6.2)
Destination Administrator External Entity
Data Structure Cancelation Report=
OrdID+
26
CutID+
EmpID+
OrdDateofPalacement+
OrdEventName+
OrdEventDate+
OrdEventTime+
OrdStatus
Name Quotation Details
Description Sends the customer details of the estimated quotations for the
event requested.
Origin/Source Quotation Process( 5.1)
Destination Client External Entity
Data Structure Quotation Details =
InvID+
LineTotal+
LineQty+
LinePayable
Name Quotation Details
Description Sends a copy of the quotation to the accounts file to be saved in
the records.
Origin/Source Quotation Process (5.1)
Destination Accounts File
Data Structure Quotation Details =
InvID+
LineTotal+
LineQty+
LinePayable
Name Quotation Details
27
Description Sends details of the quotation to the payment calculation
process to aid in the calculation on the final payment bill.
Origin/Source Quotation Process (5.1)
Destination Payment Calculation Process( 5.2)
Data Structure Quotation Details =
InvID+
LineTotal+
LineQty+
LinePayable
Name Invoice
Description Sends the Client information regarding the fees due for the
service provided by the company for organizing the event.
Origin/Source Payment Process (5.2)
Destination Client
Data Structure Invoice =
InvID+
LineTotal+
LineQty+
LinePayable
Name Invoice
Description Sends a copy of the invoice to the accounts record to store the
details of the payment outstanding from the client
Origin/Source Payment Process (5.2)
Destination Accounts File
Data Structure Invoice =
InvID+
LineTotal+
LineQty+
LinePayable
28
Name Payment Details
Description The client sends the details regarding the methods of payment
and the amount being paid to the company.
Origin/Source Client External Entity
Destination Payment Process (5.2)
Data Structure Payment Details =
InvID+
AccID+
InvPayMethod+
InvPayStatus+
InvPayable+
InvDiscount
Name Payment Details
Description Sends a copy of the payment made by the client to be stored in
the accounts file
Origin/Source Payment Process (5.2)
Destination Accounts File
Data Structure Payment Details =
InvID+
AccID+
InvPayMethod+
InvPayStatus+
InvPayable+
InvDiscount
Name Accounts Details
Description Sends records of the accounts to the report process in order to
generate the reports required by the administrator.
Origin/Source Accounts File
Destination Report Process (5.3)
Data Structure Payment Details =
29
InvID+
AccID+
InvPayMethod+
InvPayStatus+
InvPayable+
InvDiscount
Name Income and Expenditure Report / Profit and Loss Report
Description Sends the report to the administrator to view the performance
of the company financially.
Origin/Source Report Process (5.3)
Destination Administrator External Entity
Data Structure Income and Expenditure Report / Profit and Loss Report=
InvID+
AccID+
InvPayMethod+
InvPayStatus+
InvPayable+
InvDiscount
Name Allocated Staff List
Description This gives the staff files details of the staff that have been
allocated for a particular event.
Origin/Source Resource Allocation Process (4.1)
Destination Staff File
Data Structure Allocated Staff List=
EmpID+
EmpName+
EmpDoB+
EmpAddress+
EmpTele+
DeptID+
30
EmpDescription+
EmpStatus+
EmprecStatus
Name Staff Records
Description Sends the report process information about all the records in
order that the process can generate reports.
Origin/Source Staff File
Destination Report Process (4.2)
Data Structure Staff Records=
EmpID+
EmpName+
EmpDoB+
EmpAddress+
EmpTele+
DeptID+
EmpDescription+
EmpStatus+
EmprecStatus
Name Staff Event Report
Description Provided the Administrator with a report containing the details
of the events covered by different staff.
Origin/Source Report Process (4.2)
Destination Administrator External Entity
Data Structure Staff Event Report =
EmpID+
EmpName+
EmpDoB+
EmpAddress+
EmpTele+
DeptID+
31
EmpDescription+
EmpStatus+
EmprecStatus
Name Reserved Inventory List
Description Provides the inventory file with details of the requirements for
a particular event.
Origin/Source Resource Allocation Process (3.1)
Destination Inventory File
Data Structure Reserved Inventory List=
ItemID+
ItemName+
ItemDescription+
ItemSerialNumber+
ItemPrice+
ItemStatus+
ItemRecStatus+
DepID
Name Inventory Records
Description Gives the report process information to generate the reports
required by the administrators.
Origin/Source Inventory File
Destination Report Process (3.2)
Data Structure Inventory Records=
ItemID+
ItemName+
ItemDescription+
ItemSerialNumber+
ItemPrice+
ItemStatus+
ItemRecStatus+
32
DepID
Name Low supplies Report / Free Supplies Report
Description Provides the administrator information regarding the supplies
that are currently available in the stocks.
Origin/Source Report Process (3.2)
Destination Administrator External Entity
Data Structure Low Supplies Report / Free Supplies Report=
ItemID+
ItemName+
ItemDescription+
ItemSerialNumber+
ItemPrice+
ItemStatus+
ItemRecStatus+
DepID
Name Reservation Details
Description The information that is provided by the Client regarding the
booking that the client wishes to make.
Origin/Source Client External Entity
Destination Booking Process (2.1)
Data Structure Reservation Details =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
33
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Booking Details
Description This information regarding the booking which the client made
will be stored in the reservation files for future reference.
Origin/Source Booking Process (2.1)
Destination Reservation File
Data Structure Reservation Details =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Reservation Details
Description Passes the information on to the next process to check for
availability.
Origin/Source Booking Process (2.1)
Destination Check Availability Process (2.2)
Data Structure Reservation Details =
OrdID+
34
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Availability
Description Check to ensure that the stocks are available to cater to the
requested event.
Origin/Source Check Availability Process (2.2)
Destination Booking Process (2.1)
Data Structure Availability=
OrdID+
STID+
ItemID+
ItemStatus
Name Availability
Description Check to ensure that the stocks are available to cater to the
requested event.
Origin/Source Check Availability Process (2.2)
Destination Inventory File
Data Structure Availability=
OrdID+
STID+
35
ItemID+
ItemStatus
Name Availability
Description Check to ensure that the company is not fully engaged with
other prior events.
Origin/Source Check Availability Process (2.2)
Destination Reservation File
Data Structure Availability=
OrdID+
OrdEventDate+
OrdEventTime
Name Availability
Description Check to ensure that staffs are available to cater to the
requested event.
Origin/Source Check Availability Process (2.2)
Destination Staff File
Data Structure Availability =
OrdID+
EmpID+
EmpStatus
Name Availability
Description Provides the Client with information as to whether the
company is able to cater to the Clients requirements.
Origin/Source Check Availability Process (2.2)
Destination Client
Data Structure Availability =
OrdID+
EmpID+
36
ItemID+
EmpStatus+
ItemStatus
Name Reservation Records
Description Provides the process with information regarding the
reservations in order that the process may submit the required
report to the Administrator.
Origin/Source Reservation Files
Destination Report process (2.3)
Data Structure Reservation Record =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Monthly report/ annual report reservation report
Description Provides the user with detailed reports of the company’s
activities in relation to the reservations that it has made.
Origin/Source Report Process (2.3)
Destination Administrator
Data Structure Monthly report/ annual report/ failed reservation report =
OrdID+
37
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Event Details
Description Provides the resource allocation process with information
regarding the event that has been required by the client.
Origin/Source Reservation process (2.0)
Destination Resource Allocation Process (3.0)
Data Structure Event Details =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
38
Name Event Details
Description Provides the human resource allocation process with
information regarding the event that has been required by the
client.
Origin/Source Reservation process (2.0)
Destination Human Resource Allocation Process (4.0)
Data Structure Event Details =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Event Details
Description Provides the Payment process with information regarding the
event that has been required by the client.
Origin/Source Reservation process (2.0)
Destination Payment Process (5.0)
Data Structure Event Details =
OrdID+
CustID+
EmpID+
OrdDateofPlacement+
OrdEventName+
39
OrdEventType+
OrdEventDate+
OrdEventTime+
OrdEventDuration+
OrdEventLocation+
OrdDescription+
OrdStatus+
OrdRecStatus+
Name Supplier Details
Description Provides the system with details of a new supplier and details
of the product that they will be supplying.
Origin/Source Supplier External Entity
Destination Supplier Registration Process (7.1)
Data Structure Supplier Details =
SupID+
SupName+
SupAddress+
SupTel+
ProdName+
ProdType
Name Supplier Details
Description Sends the details supplied by the supplier to the Supplier File
Origin/Source Supplier Registration Process (7.1)
Destination Supplier File
Data Structure Supplier Details =
SupID+
SupName+
SupAddress+
SupTel+
ProdName+
40
ProdType
Name Product Details
Description Sends the supplier details of the products needed for an event.
Origin/Source Supplier Process (7.2)
Destination Supplier External Entity
Data Structure Supplier Details =
SupID+
ProdName+
ProdType
Name Product Details
Description Sends the required product details to the supplier file
Origin/Source Supplier Process (7.2)
Destination Supplier File Data Store
Data Structure Supplier Details =
SupID+
ProdName+
ProdType
Name Product Details
Description Sends the required product details to the supplier file
Origin/Source Resource Allocation Process (3.0)
Destination Supplier Process (7.0)
Data Structure Supplier Details =
SupID+
ProdName+
ProdType
41
42
8.3 – EXTERNAL ENTITIES
Name Client
Description This entity is the client of the company who will request the
company to organize and event for them. The client will
provide all the necessary information regarding the event and
also other information such as payment methods and
cancelations.
Input Data
Flows
Availability
Confirmation
Quotation
Invoice
Cancelation reply
Output Data
Flows
Customer Details
Reservation Details
Cancelation Information
Payment Details
Name Administrator
Description This external entity will have be and overseer of the activities
of the company. The administrator will receive all the
information regarding the company in a report format.
Input Data
Flows
Monthly report/ Annual report
Low supplies Report / Free supplies Report
Staff Event Report
Income and Expenditure report / Profit and Loss
Report
Cancelation Report
Output Data
Flows
N/A
43
Name Supplier
Description This entity is the suppliers who will provide the company
with products that it on its own cannot procure. The supplier
will provide his personal information to the system and in
return will receive details of the products that the company
wishes to obtain.
Input Data
Flows
Cancelled Product List
Product Details
Output Data
Flows
Supplier Details
44
8.4 – PROCESSES
Name 6.1 Cancelation Process
Description This process is tasked with the job of cancelling events on
request of the Client.
Input Data Flows Cancelation Information
Output Data
flows
Cancelation Reply
Deleted Reservation Records
Deallocated Staff Records
Deallocated Inventory Records
Cancelled Product List
Process
Description
BEGIN
READ Cancelation Information
UPDATE OrdStatus
END
Name 6.2 Report Process
Description This process will obtain generate reports pertaining to the
cancelation of events.
Input Data Flows N/A
Output Data
flows
Cancelation Report
Process
Description
BEGIN
GET Order Details
IF OrdStatus EQUALS “Cancelled ”
WRITE Cancelled Orders into Report
DISPLAY Report
END IF
END
Name 5.1 Quotation Process
Description This process will generate the quotation to be presented to
45
the Client in the initial stages when the Client first
approaches the company.
Input Data Flows N/A
Output Data
flows
Quotation Details
Quotation Details
Process
Description
BEGIN
READ Invoice Details
ADD Costs
DISPLAY quotation
WRITE Quotation to Accounts File
END
Name 5.2 Payment Calculation Process
Description This Process will generate the payment due at the end of the
event taking to account the cost of all requirements that the
Client wished for.
Input Data Flows Payment Details
Output Data
flows
Invoice
Invoice
Payment Details
Process
Description
BEGIN
READ Cost of Order
DISPLAY Invoice
WRITE Invoice to Accounts File
READ Payment Details
WRITE Payment Details to Accounts File
END
Name 5.3 Report Process
Description This process will generate the information regarding the
company’s monetary standings.
Input Data Flows Account Details
46
Output Data
flows
Income and expenditure report / Profit and Loss
Report
Process
Description
BEGIN
READ Accounts details from Accounts File
CALCULATE Income and Expenditure
CALCULATE Profit or Loss
DISPLAY Income and Expenditure Report and Profit
and Loss Report
END
Name 4.1 Resource Allocation Process
Description This process will allocate staff as needed for each particular
task.
Input Data
Flows
N/A
Output Data
flows
Allocate Staff List
Process
Description
BEGIN
READ Employee Details
IF Employee Status EQUAL “Available”
UPDATE Employee Status to “Unavailable”
END IF
END
Name 4.2 Report Process
Description This process will generate a report for the Administration
regarding the utilization of the company’s staff.
Input Data Flows Staff records
Output Data
flows
Staff Event Report
Process
Description
BEGIN
READ Employee Details
47
DSIPLAY Employee Records
END
Name 3.1 Resource Allocation Process
Description This process will allocate resources as needed for each
particular task.
Input Data
Flows
N/A
Output Data
flows
Reserved Inventory List
Process
Description
BEGIN
READ Inventory Details
IF Inventory Status EQUAL “Available”
UPDATE Inventory Status to “Unavailable”
END IF
END
Name 3.2 Report Process
Description This report process will generate the information regarding
the supplies that are in low quantities and also what supplies
which are free and not being utilized by any event.
Input Data Flows Inventory Records
Output Data
flows
Reserved Inventory List
Process
Description
BEGIN
READ Inventory Details
DSIPLAY Inventory Records
END
Name 2.1 Booking Process
Description The booking process will record in reservation information
48
in the appropriate file after it is ensured that the company can
carter to the request.
Input Data Flows Reservation Details
Availability
Output Data
flows
Booking details
Reservation Details
Process
Description
BEGIN
READ Reservation Details from Client
GET Availability
IF Available
WRITE Booking Details to Reservation File
END IF
END
Name 2.2 Check Availability
Description This process will check all the relevant records to ensure that
the company has all the required resources and the man
power to cater to the client’s request. Also to ensure that the
company isn’t already over booked with requests.
Input Data
Flows
Reservation Details
Output Data
flows
Availability
Availability
Availability
Availability
Availability
Process
Description
BEGIN
GET Reservation Details from Booking Process
GET Inventory Details
GET Reservation Details
GET Staff Details
IF Reservation AND Inventory AND Staff Status
49
EQUALS “Available”
WRITE Availability to Booking Process
DISPLAY Availability to Client
ELSE
DISPLAY Unavailability to Client
END IF
END
Name 2.3 Report Process
Description This process will generate a report with the annual and
monthly reservations of the company.
Input Data Flows Reservation Records
Output Data
flows
Monthly/Annual Reservation Report
Process
Description
BEGIN
GET Reservation Records
SORT by year OR month
DISPLAY Sorted Reservation Details
END
Name 1.0 Register Customer Process
Description This process will register all new clients of the company
Input Data Flows Customer Details
Output Data
flows
Customer Details
Process
Description
BEGIN
READ Customer Details
WRITE Customer Details to Customer File
END
Name 7.1 Supplier Registration Process
50
Description This processed is used register new suppliers to the system.
Input Data Flows Supplier Details
Output Data
flows
Supplier Details
Process
Description
BEGIN
READ Customer Details
WRITE Customer Details to Supplier File
END
Name 7.2 Supplier Process
Description This processed is used communicate to the supplier
regarding products needed for the event.
Input Data Flows N/A
Output Data
flows
Product Details
Product Details
Process
Description
BEGIN
GET Product Details
WRITE Product Details to Supplier File
DISPLAY Product Details to Supplier
END
51
9.0 – ENTITY LIFE HISTORY
9.1 – CUSTOMER ENTITY
Customer
Customer termination
Create Customer Mid Life Event
Give Reservation * Details
Payment *Update Reservation *
Details
Delay Reservation Cancel Reservation
52
9.2 – ORDERS ENTITY
Order
Create Order Mid Life Event Order Termination
Order Details * Check Availability *
Cancel Order Complete Order
53
9.3 – EMPLOYEES ENTITY
Employee
Add Employee Mid Life EventEmployee
Termination
Allocate Staff *
Event ManagerEvent Staffs
Allocate Event *
54
9.4 – INVOICE ENTITY
Invoice
Create Invoice Mid Life Event Invoice Termination
Customer Details * Payment Details *
Paid Advance * Total Amount Due *
55
9.5 – INVENTORY ENTITY
Inventory
Add Inventory Mid Life Event Inventory Termination
Check Inventory * availability
Allocate Event *
Supply Inventory Get Inventory
56
9.6 – SUPPLIER ENTITY
Supplier
Add Supplier Mid Life Event Supplier Termination
Supply Product *Supply Product *
Update
Product Cancelation
Delay Product
Product Price *
57
9.7 – SUBTASKS ENTITY
Sub Task
Add Events Sub Tasks Mid Life Event End Events Sub Tasks
Allocate Sub Tasks for * events
Assign Employees for Sub * Tasks
Update Sub Task *
cancel Sub Task Complete Sub Task
58
10.0 – SCREEN DESIGNS
10.1 – ADD NEW CUSTOMER
This form is used to add a new customer when they visit the company for the first
time. What the user has to do is simply enter the details into the given fields and
simply press “Save”. If the user accidently enters incorrect data he simply has to
press “Clear” and all the fields will be cleared of all data. Validation checks will
be placed in all da forms to ensure that all the data entered is in the correct format.
59
10.2 – ADD NEW EMPLOYEE
This form is used to enter the details of newly recruited employees. The user will
simply enter the details into the form’s fields and then press the “Save” button and
the details will get saved into the system. The “Clear” button will clear all da
fields to enable the user to enter new records if needed. Validation rules will be
used to make sure that the data entered is in the correct format.
60
10.3 – ADD INVENTORY ITEM
This form is used to enter the details of the newly purchased stocks and supplies.
The user will enter the details into the form and will then press the “Save” button.
This will then save the records into the system. Validation checks will be out in
place to ensure that the data entered in is in the correct format.
61
10.4 – ADD NEW ORDER
This form is used to enter the details of a newly placed order for an event
management. The user is expected to fill in the details of the event in the relevant
fields and press the “Save” button. When this is done the records will get saved
into the database for further use. This form will also have validation checks to
ensure that the data entered is correct and accurate.
62
10. 5 – SEARCH / MODIFY ORDER
This form is used by the user to modify the details of the order that has been
placed in the Add New Order form. Which the user can change the details of the
order, the user can all add subtasks for the order and also add view the subtasks
the that are associated with that particular order.
63
10.6 – ADD NEW SUBTASK
This form is used to allocate resources for a particular event. The fields for order
ID and Subtask ID will be automatically be generated. The user is expected to
enter the Department ID into the relevant field. After that the user will save the
data and move on to enter employees, suppliers and inventory items for the event.
The user will do this by pressing one of the buttons, either the “Add Employee” or
“Add 3rd
Party Supplier” or the “Add Inventory Items” buttons.
64
10.7 – ADD EMPLOYEES TO SUBTASK
This form is used to add an employee to a task. This form will inherit the
Department ID from the previous form which is the Add New subtask form. After
this when the user presses the “Search” button the data grid will display all the
employees who fall under the searched department. The form also allows the user
65
to search for employees from other departments by simply entering the new
department’s ID into the search field and pressing the “Search” button again.
After that the user will enter the selected employee’s ID in the relevant field and
press the “ADD” button and this will save the information into the database. The
user can also view all the employees that they have already added by pressing the
“VIEW ADDED” button.
66
10.8 – ADD INVENTORY ITEMS TO SUBTASK
This form is also preceded by the Add New Subtask form. This form is also used
to add resources for the event. Here the products needed will be added into the
database. The user will enter a product name or select one from the drop down list
and press the “SEARCH” button. The form will then display the product ID of the
product searched and the user can then enter that in the Product ID field and add it
67
to the database by pressing the “ADD” button. The users can after this view all
the items they have added by pressing the “VIEW ADDED” button.
68
10.9 – ADD 3RD
PARTY SUPPLIER TO SUBTASK
This form similar to the Add Subtask Inventory form, where it will also be used to
specify the items used for a particular event. The user will enter the product name
and then will press the “SEARCH” button and the system will display all the
products IDs and the suppliers. The user will then select the product ID and add it
69
by pressing the “ADD” button. After that the user can view all the products he has
added by pressing the “VIEW ADDED” button.
70
10.10 – ADD NEW 3RD
PARTY SUPPLIER
This form is used to enter the details of a newly added supplier. The form will
request the user to enter all the details of the supplier into the relevant fields. The
user will then press the “ADD PRODUCT / SERVICE” button which will take
the user to the Add Supplier Products form. After that the user will press the
“SAVE” button and the details will be saved into the system. There will be
validation checks to ensure that the data entered is in the correct format.
71
10.11 – ADD 3RD
PARTY SUPPLIER PRODUCTS / SERVICES
This form will appear after the user has pressed the “ADD PRODUCT /
SERVICE” in the Add new supplier form. Here the user is expected to enter the
details of the products that a supplier will provide. The user will enter the details
of the items the supplier will provide and will save it into the system.
72
10.12 – MODIFY CUSTOMER DETAILS
This form will be used by the system’s user to modify or delete an existing
customer record. The form will have the details of the customer about to be
modified from the previous form which is the Search Customer form. Once the
user has modified the user will press the “SAVE CHANGES” button and the
changes will be saved. Else the user can press the “DELETE” button and the
customer will be deleted.
73
10.13 – MODIFY EMPLOYEE DETAILS
This form will be used by the system’s user to modify or delete an existing
employee record. The form will have the details of the employee about to be
modified from the previous form which is the Search Employee form. Once the
user has modified the user will press the “SAVE CHANGES” button and the
changes will be saved. Else the user can press the “DELETE” button and the
employee will be deleted.
74
10.14 – MODIFY SUPPLIER DETAILS
This form will be used by the system’s user to modify or delete an existing
supplier record. To find which supplier to modify the user will press the
“SEARCH” button and find the ID of the supplier to be deleted or modified. Once
the user has modified the user will press the “SAVE CHANGES” button and the
changes will be saved. Else the user can press the “DELETE” button and the
supplier will be deleted.
75
10.15 – MODIFY 3RD
PARTY SUPPLIER PRODUCT /
SERVICE DETAILS
This form will be used by the system’s user to modify or delete an existing
supplier’s item record. To find which supplier’s item to modify the user will press
the “SEARCH” button and find the ID of the item to be deleted or modified. Once
the user has modified the user will press the “SAVE CHANGES” button and the
changes will be saved. Else the user can press the “DELETE” button and the
supplier item will be deleted.
76
10.16 – RETURN INVENTORY ITEM
In this form, when the items that were taken from the inventory by the particular
subtasks are returns to the warehouse, the PRODUCT ID is entered and the status
of the product is changed from “Unavailable” to “Available” since its been
returned and is available to be used by another task.
77
10.17 – LOAD INVOICE
The load invoice form is used to generate the invoice. To do this the form will
request the user to enter the Order ID. From this the system will generate the
invoice when the user presses the “LOAD INVOICE” button.
78
10.18 – INVOICE
This form will be where the user will be shown the invoice. Here the user will not
have to do much since the system would have gotten the details when the user
entered the order ID in the Load Invoice form. The user however will have to
enter the discount given, if any, and then calculate the bill. After this the user can
print the invoice and provide it to the customer.
79
10.19 – LOGIN
This form is the initial form that will be opened when the user starts the system.
This form will ask the user to enter their username and the password. This will
authenticate the user and decide the level of clearance that the user is authorized
for. In the event that the user enters an incorrect username or a password the
system will display an error message. When the user enters a correct username
and password the system will take the user to the main menu.
80
10.20 – MAIN MENU
The main menu form is where all the forms are linked to mainly. This form has
not been designed yet as the system is still in the prototype stage and the main
menu layout cannot be finalized as yet.
81
11.0 – REPORT DESIGNS
11.1 – PROFIT / LOSS REPORT
82
11.2 – REPORT ON SUPPLIERS AND PRODUCTS /
SERVICES THEY PROVIDE
83
11.3 – REPORT ON STAFF ALLOCATED PER EVENT
84
11.4 – EVENTS ON A PARTICULAR MONTH
85
11.5 – INVOICE
86
12.0 – DEVELOPMENT ENVIRONMENT
While designing the system, we as a team thought in terms of developing this
system in the future too so that it can be successfully implemented once the
development it done completely. Keeping in mind the knowledge of the team
members of the project and the clients requirements we decided to develop the
system in the following methods.
12.1 – LANGUAGE OF PROGRAMMING
All 3 members of the group were well versed in Visual Basic.net, C
Programming, C++ Programming, Java Programming and C# Programming. And
after much discussion, we unanimously decided to develop the system in C# since
we have not previously developed a fully-fledged system in that language as well
as taking on the project as a challenge to test our knowledge in this language.
12.2 – PROGRAMMING TOOLS
All three members of the group were well accustomed to use and program using
Microsoft Visual Studio 2010 and since we decided to go ahead using this IDE
software tool to develop the system too. We would be using the Microsoft .Net
Framework 4.0 as it is one of the latest standards in the industry.
12. 3 – DATABASE
Since it is an obvious fact that a system of this magnitude needs to be linked with
a server to store and retrieve data from, we decided to use the Microsoft SQL
Server 2008 for this purpose. The integration between Ms SQL Server and Ms
Visual Studio 2010 is very close; it would be easy to work with this database
technology. Also the security concerns were looked into when the decision was
made.
87
13.0 – BIBLIOGRAPHY
Gerri Akers, 1999. What is Prototyping? [Online] Available at:
http://www.umsl.edu/~sauterv/analysis/prototyping/proto.html [Accessed 3
February 2012].
Smith, S., 1999. SSADM (Structured Systems Analysis & Design Method).
[Online] Available at:
http://searchsoftwarequality.techtarget.com/definition/SSADM [Accessed 30
January 2012].
www.benefitof.net, n.d. Benefits Of SSADM. [Online] Available at:
http://benefitof.net/benefits-of-ssadm/ [Accessed 30 January 2012].
www.edrawsoft.co, n.d. SSADM Diagram Software. [Online] Available at:
http://www.edrawsoft.com/SSADM.php [Accessed 30 January 2012].