SDM

Submitted By: Charith Devaka Sooriyaarachchi Maheeka Jayasuriya Suhail Jamaldeen CB003344 CB003346 CB00
Submitted To: Ms. Zeenath Hidaya
Module Title and Code: CE00321-2 System Development Methods
Intake Code: HF09B1SE
Assignment Title: Boca Juniors Management System
Date Assigned:
Date Due: 05th July 2010
System Development Methods
CE00321-2
Table of Contents
Table of Contents ............................................................................................................................ 1 1.0 Introduction ............................................................................................................................... 3 2.0 Schedule Planning..................................................................................................................... 5 Gantt chart................................................................................................................................... 5 PERT Chart ................................................................................................................................. 6 Work Load Matrix ...................................................................................................................... 7 3.0 Selection of Methodology ......................................................................................................... 8 4.0 Problem Analysis Current System ....................................................................................... 14 5.0 Overview - Proposed System .................................................................................................. 16 6.0 Process Model for the Proposed System................................................................................. 21 Context Diagram ....................................................................................................................... 21 Level 0 DFD.............................................................................................................................. 22 Level 1 DFDs ............................................................................................................................ 23 Level 2 DFD.............................................................................................................................. 30 Process Specification ................................................................................................................ 32 7.0 Data Models for the Proposed System .................................................................................... 35 Entity Relationship Diagram..................................................................................................... 35 8.0 Data Dictionary for the Proposed System............................................................................... 36 Processes ................................................................................................................................... 36 External Entities ........................................................................................................................ 41 Data Stores ................................................................................................................................ 43 Data Flows ................................................................................................................................ 45 Asia Pacific Institute of Information Technology 1
CE00321-2
9.0 Event Model for the Proposed System.................................................................................... 51 Entity Life History .................................................................................................................... 51 10.0 Interactive Screen Design ..................................................................................................... 59 Intranet Application .................................................................................................................. 59 Screen Designs ...................................................................................................................... 59 Report Designs ...................................................................................................................... 68 Internet Application .............................................................................................................. 73 11.0 Programming Environment................................................................................................... 80 Reference ...................................................................................................................................... 81
Asia Pacific Institute of Information Technology
CE00321-2
1.0 Introduction
Boca Juniors is a popular Argentines Sports Club, best known for its football team. The club has a very good performance rate in football. Therefore, this project focuses on developing an information management system called Boca Juniors Management System (BJMS) to systematically manage its tasks. The system needs to focus on two aspects. One is the website of the club to be accessed by the general public, and other is the club management system that will be used by the club management staff.
The objectives of the system were identified as below.
General users (users of the club website) must be able to, View news and updates of upcoming and past events View player profiles View souvenir items details
Players must be able to, Make reservations for sport apparels Other tasks provided for general users
Management staff must be able to, Register new players for the club Register contractors for maintenance of stadium 3
System Development Methods Manage maintenance of the stadium Create contracts for maintenance issues and assign contractors Review progress of contracts Make payments for the contractors Register suppliers for purchasing sport apparels Make orders for new sport apparels required Manage inventory of sport apparels Make payments for suppliers Manage players salary and make payments Manage players claims and make payments Manage players bonuses and make payments Generate management reports of the club
CE00321-2
CE00321-2
2.0 Schedule Planning

Gantt chart
CE00321-2
PERT Chart
CE00321-2
Work Load Matrix
Components Introductory Section Selection of Methodology. Problem analysis-current system Overview-proposed system Process Model DFD Process Specification Data Model ER Diagram Data Dictionary Event Model Entity Life History Screen Design Implementation Programming Environment The Documentation
Marks Allocation 10
Charith
6.67%
Maheeka
27%
Suhel
66.67% 100% 100%
20%
80% 70% 40% 100% 10% 20%
20
20% 40%
20
23% 45% 40% 40% 90% 66.67%
23% 45% 40% 40% 10% 16.66%
55% 10% 100% 20% 10%
20 15 15
16.66%
100.00% 33.33% 33.33% 33.33%
CE00321-2
3.0 Selection of Methodology
Development of an information management system called Boca Juniors Management System (BJMS) for the management of Boca Juniors Football Club is the objective of this assignment. In order to select a suitable methodology for the development of the system, we took in to concern some of the traditional methodologies. A methodology was selected from among Systems Development Life Cycle (SDLC), Structured Systems Analysis and Design Method (SSADM) and prototyping. Selection of the methodology was done based on the project requirements and various technical, organizational, project and team considerations.
System Development Life Cycle (SDLC) SDLC faces rapid changed in its process by adding new features daily. According to Alexandrou, (2010) Various SDLC methodologies have been developed to guide the processes involved, including the waterfall model (which was the original SDLC method) ; Rapid Application Development (RAD) ; Joint Application Development (JAD) ; the fountain model; the spiral model; build and fix; and synchronize-and-stabilize. SDLC is a systemic is a traditional and systemic approach to solve specially business problems.
System Development Methods There are seven stages in System Development Life Cycle. 1. Identifying problems, opportunities and objectives. 2. Determining information requirements 3. Analyzing the system needs. 4. Designing the recommended system. 5. Developing and documenting software 6. Testing and maintaining the system 7. Implementing and evaluating the system
CE00321-2
Advantages Suitable for larger projects The phases offer detailed steps and well defined. Clear phase for documenting. Ease of maintenance. (Anon, n.d.)
Disadvantages Increased development cost and time. (Anon, n.d.) Poor model for object oriented programming.
Structured Systems Analysis and Design Method (SSADM) SSADM is a methodology which is used widely in industries as well as in students projects (Anon, n.d.). According to Computer Systems Odessa Corporation (2010); SSADM is based on the data flow diagrams. At the early stages of projecting at description of models (functional, informational and event-trigger) the top-down method is used. SSADM is build with six stages: 0. Feasibility study 1. Investigation of the current environment 2. Business systems options Asia Pacific Institute of Information Technology 9
System Development Methods 3. Definition of requirements 4. Technical system options 5. Logical design 6. Physical design (TechTarget, 2010) SSADM includes three techniques. Logical Data Modeling
CE00321-2
This is the process of identifying, modeling and documenting the data requirements of the system being designed. The data are separated into entities (things about which a business needs to record information) and relationships (the associations between the entities). Data Flow Modeling This is the process of identifying, modeling and documenting how data moves around an information system. Data Flow Modeling examines processes (activities that transform data from one form to another), data stores (the holding areas for data), external entities (what sends data into a system or receives data from a system), and data flows (routes by which data can flow). Entity Behavior Modeling This is the process of identifying, modeling and documenting the events that affect each entity and the sequence in which these events occur. (Select Business Solutions, 2010) Advantages Strict guidelines and rules needs to be followed which will lead to huge success. Easy to identify the logical and physical aspects of the system. Well defined techniques are used.
Disadvantages Huge expenses in training people to use the technique. (Anon, nd) 10
System Development Methods Prototyping Methodology
CE00321-2
Prototyping methodology allows developers to create portions of the solution to demonstrate functionality and make needed refinements before developing the final solution (Bowman, 2009) Prototyping methodology mainly targets the end users. The beginning o f the prototyping is communication. The requirements for the new system is analyzed which will lead to the development process. In development process the prototype is created. Then the prototype is handed over to the customer. The customer will evaluate the prototype and will provide the feedback. Then the developer comes up with new corrected version what the client or the user wish. This process is repeated until it meets user requirements. At last after the fulfilling most of the needs the final system will be delivered to the customer. following the above model. 1. Communication 2. Quick plan 3. Modeling design 4. Construction of prototype 5. Deployment delivery and feedback (Stylusinc.com, 2008) There are five main stages in
(Source: Pressman R., 2003)
11
System Development Methods Advantages More interactions between users and developers. Will come up with flexible design.
CE00321-2
More user friendly system can be expected or confusing, difficult functionalities can be eliminated. The numbers of missing function will be eliminated. Not cleared objectives can be eliminated.
Disadvantages Less problem identification. The requirements of the clients may change rapidly. May lead to poor design aspects because the poor knowledge of users. May not be able to meet the dead line. First time quick prototyping may lead to bad opinion to the client on the developers.
Justification Our team is advised to come up with a traditional methodology in order to build the required web based management systems solution for the Boca Juniors Football Club. We have selected Prototyping methodology in order to build the system. According to the assignment we should select a traditional methodology. Prototyping is a traditional methodology. Also, we should only come with the target systems protot ype. So we might come up with more than one prototype in order to make the clients satisfaction. So to select the most suitable prototype, several evaluations will need to be done. These evaluations are in- line with the prototyping methodology. Prototyping methodology is often recommended to develop online system or web based applications. (Anon, nd) Boca Juniors Foot Ball Club needs an online system for the players to interact. The management system, though it runs on a private network is also web based.
12
CE00321-2
Football players are also included into the end users who may be having lack of knowledge in using systems. Since the developers provide a model of a working system. So at the end of the development a better solution will be provided for the players as well to use the system.
13
CE00321-2
4.0 Problem Analysis Current System
The project needs to provide an automated system to meet the requirements. The system needs to have abilities to perform, i. ii. iii. iv. Registration of new players Purchase of sport apparels shirts, shorts, boots, gloves, etc Maintenance of stadium Managing of players payroll a. Match playing bonus b. Goal bonus c. Claims d. Salary increments etc Providing a solution to meet these problems is the primary concern. The proposed system will provide procedures as to handle these operations. Further discussion of the procedure for handling each of the above operations is discussed in the next chapter.
Some of the problems that could be identified by thinking in terms of a manual system are discussed below. 1. Take longer time to retrieve information and poor data retrieval. There are a lot of details which were stored form 1905. So it is not easy to retrieve a detail of a person from all the details which were maintain before 100 years. Also it will harder to find out any information urgently.
2. Difficult to maintain the authentication. In some occurrence you have to go through all files to find out some specific information. So it may be difficult to prevent one person to access some files in some instances. It will make harder to maintain the security.
14
System Development Methods 3. Every paper based system face a basic problem.
CE00321-2
It may get damaged or loss of data due to accident, fire or any other disaster. Loosing data will lead to heavy loss for an organization. 4. Should appoint more officers to handle each process. Entering each and every detail to files by one person is difficult compare to a computerized system. So its easy and faster to enter details to a computerized system.
5. Cannot carry where we want It is very hard to carry all the files everywhere. The proposed system is a web based system which allows the user to access the system from where they want.
6. More time in making a report The manual system will take a lot of time to create a report. All the data should be analyzed manually and should come up with a manual report. If it is a computerized system it will take less than couple of minutes to create a report as we want.
7. There are a lot of probabilities to misplace the data and very hard to carry and access from any where we want.
15
CE00321-2
5.0 Overview - Proposed System
We decided to develop two systems for the club. One system acts as the website of the club. It is designed as an internet application. The users of this internet based system are the general public who accesses the system as fans of the club. (Note: The users who use this general view will be referred to as general users here after) The players of the club also have access to this website and perform tasks by login to the system with the authentication details provided to them when registering in the club. Second system is intranet based. It handles the management level functionalities given above. The management staff will login to the system to perform these tasks. The tasks each user can carry out are defined in the introduction chapter. In this chapter, we discuss the details about these tasks.
General Users 3.1 Vie w news and updates of upcoming and past events The home page of the website will include the details about the upcoming events. They can also view results of the previous events of the club. The details include the tournament, venue, dates of matches, teams that play for the tournament etc. These information will be available in both home page and matches page. 3.2 Vie w player profiles Players who play for the club will have their player profiles. These profiles can be viewed in the website in the players tab. This contains information about the player personal details, their match performances and their participation in upcoming events 3.3 Vie w souvenir ite ms details The club has its own souvenir items that can be bought by anyone at the club souvenir shop. The website includes details about these items in the apparels tab. The item names, brands, prices and also images of the items. The users can visit club souvenir shop to buy these items.
16
System Development Methods Players
CE00321-2
The players have to visit the club website with their authentication to be able to perform certain tasks. Otherwise, they will also be considered as general users of the system. 3.4 Make reservations for sport apparels The players can make reservations for their sport apparels. Originally they are provided a quota of items. This quota of items will be offered free of charge by the club. In case of apparels that exceeds this quota of items, will have to be either bought by the player personally or has to be made a claim where reasonable issues had arise (e.g., injury causing damage to clothes). To buy apparel he can either visit the sport apparels distributions authorities of the club and buy manually or make a reservation through the website. When making a reservation for the apparels, the procedure is to first visit the apparels tab and select an item. Once apparel is selected, the player can specify the size and the quantity he needs. If the quota of apparels assigned for him hasnt exceeded, he can just make the reservations and collect the apparels from the club. In case, the quota has exceeded he can make a reservation and visit the club and get the apparels after making payments for them. In reasonable situations he can make a claim for the apparels and get the club to pay him the cost of the apparels he purchased.
Management Staff 3.5 Register new players for the club This refers to the process of registering new players to the club. Players will provide their details and after making necessary verifications from the system side, the players will be registered. Once they are registered, they get the opportunity of playing for the club team to represent tournaments. Their profile will appear in the club website. They will also be provided a login for the website. With this login, they can perform the above mentioned task of making reservations for sport apparels. 3.6 Register contractors for maintenance of stadium Asia Pacific Institute of Information Technology 17
CE00321-2
This is the process of registering contractors for the maintenance tasks of the system. The contractors will be of different fields and specialised for those tasks. The system maintains a separate table with the contractors details that will be accessed later when maintenance issues arise. 3.7 Manage maintenance of the stadium Maintenance is vital in terms of keeping up the durability of the stadium. There are maintenance logs that need to be kept track of. There is daily, weekly and even annual check- ins. This process needs to keep track of these and check the status of these maintenance issues. With this information the management staff can make necessary decisions to make sure that the maintenance will be handled. This results in assigning new contractors to handle maintenance and to check their progress. 3.8 Create contracts for maintenance issues and assign contractors Once a maintenance issue is identified it will need to accomplish by assigning a contractor to it. The system will retrieve the maintenance issues and also the contractors who are specialised in that category. The staff will be able to assign a contractor to the issue and create a contract. Afterwards, the contractor will have to be informed about the issue. The maintenance issues will be created with the help of an external system. 3.9 Review progress of contracts When the contracts have been assigned there must be a process as to keep track of its progress. The status of the contracts, as to whether completed or still in progress will be identified and the relevant decisions can be made by the management staff. 3.10 Make payments for the contractors
Once a contract is being completed, contractors will have to be paid. After receiving the invoice for the contract necessary steps to make payments to the contractors will be taken. 3.11 Register suppliers for purchasing sport apparels
This process is similar to registering contractors. The suppliers will be registered for the purchase of sport apparels for the club. They will be specialised in certain apparels and apparels
18
CE00321-2
will be purchased accordingly. When need for the apparels arise, the system will check for the suppliers for the relevant apparels and do the purchasing. 3.12 Make orders for ne w sport apparels required
When there arise a need for apparels, they need to be purchased from the relevant suppliers. This process is to determine the apparel types needed the quantity, etc and make purchase orders to the suppliers. The list of apparels that needs to be purchased will be generated with help of players apparel reservations and stock details. 3.13 Manage inventory of sport apparels
Once the purchase order is made and the goods are received, they will be checked with the purchase order for the quantity and types. Quality of the apparels will also be checked and the goods will be accepted. When the goods are accepted they will be added to the inventory of apparels and will be made available for the players and other customers. 3.14 Make payments for s uppliers
After the goods have been accepted the supplier will issue an invoice. Payments to the supplier must be made according to the invoice. This can also be handled by the system. 3.15 Manage players salary and make payments
The players will be played monthly by the club. The salary depends on the player level and their experience. The system will check the salary details of the players and generate the salary slips for them. 3.16 Manage players claims and make payments When players make claims for medical reasons or damages of apparels, the system will verify the claim requests. First it will check whether there is enough amount of claiming quota remaining and then check whether the request is valid and acceptable. In the case of an accepted claim, the player will be paid back for the expenses he had to make. 3.16 Manage players bonuses and make payments
Bonuses for the players will be calculated depending on their participation and performance in matches. When they participate in a match, they will get a bonus. If they have scored any goals Asia Pacific Institute of Information Technology 19
CE00321-2
in the match it will also add up as a bonus. The result of the match will also effect in calculating the bonus. If the match had been won, the bonus will be higher. The details about matc h performances will be added to the system database via an external system to this system. 3.17 Generate manage ment reports of the club
The system must be able to generate reports covering all the processes carried out by the club. This will be available for the management level users of the club. The reports include Players performance reports Match details reports Maintenance issues reports Contracts reports Contractor reports Supplier reports Player payroll details reports Payment details reports Inventory reports Reservation reports Purchase details reports
20
CE00321-2
6.0 Process Model for the Proposed System

Context Diagram
Contractor Details
Player Details Player Registration Details Contractor Registration Confirmation Note
Contractors
Rejected Player Registration Note Rejected Contractor Registration Note Player Contract Completed Novice Rejected Claim Note
Maintenance Details
Accept Contract Notice
Bonus payment Details
Claim Details
Invoice
Claim Payment Details
Apparel Details
Boca Juniors Management System (BJMS)
Claim Payment Details
Good Received Note Purchase Order
Maintenance Data
Payment Details
Pending Maintenance Data

Match Performance Data
Supplier Details
Invoice
Supplier Supplier Registration Confirmation Note Rejected Supplier Registration Note
Insert Maintenance
Add Apparel System
Match Performance System
21
CE00321-2
Level 0 DFD
Level 00
Player Registration Details Player Details Rejected Player Registration Note
1.0 Register Player
Player Data
Player
Updated Payroll Details Match Performance System
Player
Bonus
Match Performance Data Bonus Payment Details
Payroll Data Salary Payment Details Salary
Rejected Claim Note
Claim Details Bonus payment Details Claim Payment Details Salary Slip
2.0 Manage Player Payroll Claims Payment Details Claims
Payments
Purchase Payment Data New Apparel Data 3.0 Handling Purchases Made Payments Payment Details Good Received Note Apparel
Contractor
Contractor Data
5.0 Register Contractors Contractor Registration Confirmation Note Contractor Details Rejected Contractor Registration Note
Add Apparel System
Supplier Data Suppliers
Purchase Order
Made Payments
Contractors Contract Completed Maintenance Notice Details
Supplier Data
Invoice
Payment Details
Contractor Details Contract Payment Details
Accept Contract Payment Invoice Notice Details
4.0 Register Supplier
Supplier Details Supplier Registration Confirmation Note Rejected Supplier Registration Note
Supplier
6.0 Handling Maintenance Pending Maintenance Data Contracts Contract Data Maintenance Data Insert Maintenance System Apparel Details 7.0 Apparel Reservation and Purchase
Apparel Reservation
Apparel Details
Player Details Available Apparel Details
22
CE00321-2
Level 1 DFDs
1.0 Register Player
Player Details
Player
1.1 Receive Player Details
Player Detail
Reject Player Registration Note 1.2 Verify Details
Accepted Player Details
Player Registration Note 1.3 Register Player Player Data Player
23
CE00321-2
2.0 Manage Players Payroll

Bonus Payment Data Match Performance Data Matches Bonus Payment Details Player 2.2 Handling Bonus
Match Details
Claim Payment Details Handle Match Details Rejected Claim Note Claim Details Bonus Details
Bonus Data 2.1 Handling Claims Accounts Payment Data Claim Details 2.3 Get Payroll Details
Payroll Details Updated Payroll Details 2.4 Update Payroll Details Players
Salary Slip
Claim Data
Salary Data
Salary Data
Salary Payment Details
2.5 Pay Salary
24
CE00321-2
3.0 Handling Purchase
Purchase Order 3.2 Raise Purchase Order Invoice
Identify Purchase Apparel
Suppliers
Apparel Data
Apparel Data
Order Incomplete Notice Payment Details
3.1 Select Supplier
3.3 Receive Apparel Good Received Note Received Apparel Details
Supplier Data
Suppliers
3.6 Pay Supplier
Payment details
3.4 Verify Received Apparel
Verified Apparel Details
Apparel
New Apparel Data
3.5 Update Inventory
25
CE00321-2
4.0 Register Suppliers
Supplier Details
Supplier
4.1 Receive Supplier Details
Supplier Detail
Reject Supplier Registration Note 4.2 Verify Details
Accepted Supplier Details
Supplier Registration Note 4.3 Register Supplier Supplier Data Supplier
26
CE00321-2
5.0 Register Contractors
Contactor Details
Contactor
5.1 Receive Contractor Details
Contactor Detail
Reject Contactor Registration Note 5.2 Verify Details
Accepted Contactor Details
Contactor Registration Note 5.3 Register Contactor
Contactor Data
Contactor
27
CE00321-2
6.0 Handling Maintenance
Contractor
Contractors
Determine Maintenance Issue Maintenance Data
Invoice
Accept Maintenance Contract Notice Details
Payment Details
Contractor Details
Maintenance
Pending Maintenance Data
6.4 Handle Contract
Assigned Contactor
6.3 Assign Contractor
Maintenance Data
6.2 Get Maintenance Data
Contract Details Contract Completed Notice Contractors Payment Details 6.5 Verify Contract Details Contract Payment Details
6.6 Pay Contractor
Contract Payment Details
Accounts
28

7.0 Apparel Reservation and Purchase
CE00321-2
Payment Details Apparel Details Players
Player
Apparel Details
7.5 Sell Apparel
Player Details Apparel Details 7.3 Reserve Apparel s Un available Apparel Details
7.2 Verify Apparel Request
Apparel Details
7.1 Receive Apparel Reservation
Apparel Details
7.4 Receive Apparel Details
Available Apparel Details
Apparel Details
Apparels Apparel Details
Apparel Reservation
7.4 Receive Apparel Purchase Request
Apparel Details
29
CE00321-2
Level 2 DFD
2.1 Handling Claims
Player
Claim Details
2.1.1 Receive Claim Request
Claim Details
Rejected Claim Note
2.1.2 Verify Claim
Claim Details
Accepted Claims
Claim Payment Details 2.1.3 Pay Claim Claim Payment Details Accounts
30
CE00321-2
2.2 Handling Bonus
Player
Bonus Details Bonus Payment Details
To 2.4
Bonus Data 2.2.4 Pay Bonus
2.2.3 Calculate Bonus Bonus Details
Accepted Bonus
2.2.1 Verify Bonus
Performance Details
Bonus Details 2.2.2 Get Match Details
Performance Details
Accounts
Matches
Match Performance Details
31
CE00321-2
Process Specification
Process 2.1.2 Verify Claim

1 Y Y X 2 N X 3 N X
Valid claim Claim balance available Accept claim Reject claim
Process 2.2.1 Verify Bonus

Match played Goals scored Match won Match bonus Goal bonus Special bonus 1 Y Y Y X X X 2 N 3 Y N Y X X 4 Y N N X 5 Y Y N X X
Process 2.2.3 Calculate Bonus BEGIN IF (Match Played) BEGIN Bonus = Match_Bonus IF (Match Won) BEGIN IF (Goal Scored) BEGIN Goal_Bonus = Amount * No_of_Goals Asia Pacific Institute of Information Technology 32
CE00321-2
Bonus = Match_Bonus + Special_Bonus + Goal_Bonus END IF END IF ELSE BEGIN Bonus = Match_Bonus + Special_Bonus END ELSE END Process 3.4 Verify Received Apparel
1 Y X X X 2 N
All items received Pay supplier Update inventory Issue goods received note Issue order incomplete note
6.5 Verify Contract Details

1 Y X X 2 N
Contract completed Pay contractor Issue invoice
7.2 Verify Apparel Request

1 Y X X 2 N X
Apparel available Reject reservation Sell apparel Issue receipt
33
System Development Methods 6.3 Assign Contractor BEGIN GET contract details SELECT contract type SELECT contractor END
CE00321-2
34
CE00321-2
7.0 Data Models for the Proposed System

Entity Relationship Diagram
Contract ID Maintenance ID Cost Completed Date
Maintenance ID Maintenance Type Location Maintenance Level Description Status
Maintenance
has has
Maintenance Detail
has
Contract
Bonus ID Amount Player ID Date Bonus Type Match ID
Contract ID Contractor ID Description Start Date Due Date Finish Date Status Total Cost
Claim ID Amount Player ID Date Claim Type
Salary ID Amount Player ID Date
Contractor Payment
Contract ID Date of Payment Invoice No Total Amount has
Bonus
Has
Claim
Salary
Has Has
Contractor
Player ID Name Age User Name Password Salary Claim Threshold Date Joined Position Team Email Telephone Has Contractor ID Name Address Telephone No Contract Type
Player
Supplier
Supplier ID Name Address Telephone No Apparel Type Apparel Description
Match Detail
Match ID Player ID Goals Notes Has
Has
Apparel Order ID Apparel ID Type Quantity Price(free/pur)
Purchase Order ID Date of Payment Invoice No Total Amount
Supply Payment
Has
Apparel Order Details Match

Match ID Result Date and Time Home Team Opposing Team Location Score
Has
Purchase Order ID Apparel ID Quantity Unit Price Date of Supply
Purchase Order Detail

Has Apparel Order ID Player ID Request Date Total Cost Status (res/ord) Receipt No Collected Date Has Has
Has
Purchase Order
Purchase Order ID Supplier ID Total Amount Ordered Date Status
Player Apparel Order
Apparel
Apparel ID Name Type Size Unit Price In-hand Quantity Sold Quantity
35
CE00321-2
8.0 Data Dictionary for the Proposed System

Processes
Name Description 1.0 Register Player Register all the players by providing the details. As the player provide the details the process will check for verification and let to know the player weather is accepted or not. All the details will be saved in Player table. Input Data Flows Output Data Flows Player details from Player Player registration details to Player Rejected Player registration note to Player Player data to player table. Process BEGIN READ Player registration details CHECK Player registration details SEND acceptation or refusal letter STORE player data END
Name Description
2.0 Manage Player Payroll Once the player claim for money in any purpose this process check for validation to accept the claims or not, and send the claim money or reject notification to the player. The validation will be done using the player details form Player File and the performance in matches using Matches File. This process offer salary and the slips. The details of the salary and claims were saved in specific files
Input Data Flows
Match Performance Data from Player Matches Claim Details from Player Payroll Data from Player file. Bonus payment Details from Player 36
System Development Methods Output Data Flows Bonus Payment Details to Bonus table Rejected Claim Note to Player Claim Payment Details to Player. Salary Slip to Player. Salary Payment Details to Salary Updated Payroll Details to Player file BEGIN READ Bonus payment Details CHECK Player Details IF acceptable Pay Bonus UPDATE Bonus ELSE IF not acceptable Send reject Note END Process BEGIN READ Claim Details CHECK Player Details, Matches IF acceptable Pay Claim UPDATE Claim ELSE IF not acceptable Send reject Note END
CE00321-2
Process
Name Description
3.0 Handling Purchases Once it is decided to purchase new apparel, will send the order to registered supplier. Then the supplier will provide the needing goods along with the invoice and then the supplier will offered Good received note. The purchased goods will be updated to the purchase file.
37
System Development Methods Input Data Flows Output Data Flows Supplier Data from Suppliers file. Invoice from Supplier. Purchase Payment Data to Payments File. New Item Data to inventory file Purchase Details to Purchase File Purchase Order to supplier Payment Details to Supplier. Good Received Note to supplier BEGIN CHECK Supplier data SEND Purchase Order READ invoice UPDATE Inventory UPDATE Purchase Details UPDATE Payments Table
CE00321-2
Process
SEND Payment & Good Received Note END
Name Description
4.0 Register Supplier The registrations of the new Supplier take effect here. The supplier provides the details. The validation of the details was done and then the acceptance or reject note was sent to the suppliers. The details of the accepted suppliers were saved in the supplier file.
Input Data Flows Output Data Flows
Supplier Details from Suppliers. Suppliers to Supplier File. Supplier Registration Confirmation Note to Supplier. Rejected Supplier registration note to Supplier. BEGIN READ Supplier data IF Supplier data accepted SEND Registration Confirmation Note
Process
38
System Development Methods SAVE supplier details ELSE IF Supplier rejected END IF END
CE00321-2
Name Description
5.0 Register Contractors The registrations of the new contractors take effect here. The contractors provide the details. The validation of the details was done and then the acceptance or reject note was sent to the contractors.
Input Data Flows Output Data Flows
Contractor Details from Contractors Contractor Data to Contractor File Contractor Registration Confirmation Note to Contractors. Rejected Contractor Registration Note to Contractors BEGIN READ Contractor Details CHECK Contractor Details IF Contractor Details accepted SEND Registration Confirmation Note SAVE Contactor details ELSE IF Contractor rejected. SEND Rejected Note END IF END
Process
Name Description
6.0 Handling Maintenance Pending maintenance data will be gathered from maintenance file and the details will be sending to contractors. As soon as the contactor receives the details he will send an acceptance note. After finishing all the works the contractor will send an invoice. After the payment the system will update accounts file.
39
System Development Methods Input Data Flows Pending maintenance details from Maintenance file. Contractor completed notice from Contractors Contractor Details from Contractor file Accept Contractor Details from Contractors. Contractor payment details to Accounts File Maintenance details to Contractors Invoice to contractors Payment details to contractors Maintenance data to Maintenance file BEGIN READ Pending maintenance details SEND Pending maintenance details READ Contract accepted/ rejected notice READ Contract Completed details SEND Payment Details UPDATE Accounts file END
CE00321-2
Output Data Flows
Process
Name Description
7.0 Handle Apparel Reservation and request The details of the Apparels which are needed to a player will be received and the player details will be verified. Then the available Apparels will be checked from the inventory and produced or the Apparel will receive.
Input Data Flows
Output Data Flows Process
Apparel details from the Player. Player details from Player File Available Apparel details from Inventory. Apparel details to Apparel reservation file BEGIN READ Apparel Details. READ Player details CHECK Inventory File IF Apparel available Offer Apparel
40
System Development Methods ELSE Reserve Apparel END
CE00321-2
External Entities
Name Description
Input Data Flows
Output Data Flows
Player The player should give his details in order to register with the club. Also as soon the player got registered to the system he will get various services from the club by the system. Salary, bonus, T-Shirts are some of the services. The player should give details as he is need of a particular service. Player Registration Details from process 1.0, Register Player Rejected Player Registration Note process 1.0, Register Player Rejected Claim Note process 2.0 Manage Player Payroll Claim Payment Details from process 2.0 Manage Player Payroll Salary Slip from process 2.0 Manage Player Payroll Parent details to process 6.0,Register Customer Request membership to process 6.0,Register Customer Customer details to process 6.0,Register Customer Feedback to process 8.0, Process feedback Request new Apparels to process 7.0, Request New Apparels Purchase request to process 2.0, Purchase Apparels Payment details to process 2.0, Purchase Apparels Payment details to process 3.0, Return Apparels Return details to process 3.0, Return Apparels Request renewal to process 4.0, Extend Loan Borrowing request to process 1.0, Borrow Apparels
Name Description
Input Data Flows
Contractor The contractor provides details in order to register. As he registered with the system he will receive maintenance data which should be done. He will maintain the specific pending process and will give the invoice and get paid. Contractor Registration Confirmation Note from process 5.0 Register Contractors Contractor Registration Confirmation Note from process 5.0 Register Contractors 41
CE00321-2
Output Data Flows
Rejected Contractor Registration Confirmation Note from process 5.0 Register Contractors Invoice from process 6.0 Handling Maintenance. Payment details to process 6.0 Handling Maintenance Maintenance details from process 6.0 Handling Maintenance. Contractor Completed Invoice to process 6.0 Handling Maintenance. Accept Contract Notice to process 5.0 Handling Maintenance Contractor Details to process 5.0 Handling Maintenance
Name Description
Input Data Flows
Output Data Flows
Supplier The supplier gets registered by providing needed details. Suppliers provide the goods which are needed to the club as well as the players. They offer invoice and get paid. Purchase Order from process 3.0 Handling Purchases Payment details from process 3.0 Handling Purchases Good received note from process 3.0 Handling Purchases Supplier registration confirmation note from process 4.0 register supplier. Rejected supplier note from process 4.0 Register Supplier. Invoice to process 3.0 Handling Purchases. Supplier Details to process 3.0 Handling Purchases.
Name Description Input Data Flows Output Data Flows
Add Apparel System An external process will calculate what are the apparels are needed and will enter the details to the system. The details of the apparels.
Name Description Input Data Flows Output Data Flows
Insert Maintenance System The maintenance details will be reviewed by an external entity and will again give to the system. Maintenance Data Pending maintenance Data
42
System Development Methods Name Description Input Data Flows Output Data Flows
CE00321-2
Match Performance System The match performance details will be an input to the system as an external. These details will be used for bonus, payroll and claims. n/a Match performance details
Data Stores
Name Description Input data flows Output data flow Data structure
D1 Player Stores details of registered player Player data from process 1.0 Register Player. Updated payroll details from process 2.0, Manage Player Payroll Payroll data to process 2.0, Payroll Data Player details to process 7.0, Apparel Reservation and purchase = Player ID + Name +Age + User Name + Password + Salary + Claim Threshold + Date Joined + Position + Team + Email + Telephone
D2 Inventory Stores the details of the items which were purchased and provide the details of available items whenever the user wants. New item data from process 3.0 Handling Purchases. Available item details to process 7.0, Handle Item request.
D3 Suppliers Stores details of suppliers who are registered with the system. Supplier data from process 4.0 Register Supplier. Supplier data to process 3.0, Handling purchases. = Supplier ID + Name + Address + Telephone No + Apparel Type + Apparel Description
Name
D4 Matches 43
System Development Methods Description Input data flows Output data flow Data structure Stores the static details of matches played.
CE00321-2
Match performance data to process 2.0, Manage player Payroll. = Match ID + Result + Date and Time+ Home Team + Opposing Team + Location + Score
D5 Payments Payments to the suppliers are stored in this file.
Name Description
Input data flows Output data flow Data structure
D6 Maintenance All the details of the maintenance were stored here. Pending maintenance details were accessed from the file and the details were passes to the contractor to make him done. Maintenance details from process, 6.0 Handling maintenance. Pending Maintenance data to process 6.0, Handling Maintenance. =Maintenance Detail ID + Contract ID + Maintenance ID + Cost + Completed Date
D7 Contracts Details of contracts will be saved. Contract details from process, 6.0 Handling maintenance. N/A = Contract ID + Description + Start Date + Due Date + Finish Date + Status + Total Amount
D8 Salary Salary details of the player will be saved here. Salary Payment Details from process, 2.0 Manage Player Payroll. N/A = Salary ID + Amount + Player ID + Date 44
CE00321-2
Data Flows
Name Description Origin/Source Destination/Sink Data structure
Player Details The player gives their details to system in order to register themselves. Player 1.0 Register Player = Player ID + Name + Age + User Name + Password + Salary + Claim Threshold + Date + Joined Position + Team+ Email + Telephone
Player Registration Details The system provides the player his details if it is accepted. 1.0 Register Player Player = Player ID + Name + Age + User Name + Password + Salary + Claim Threshold + Date + Joined Position + Team+ Email + Telephone
Rejected Player Registration Note The system provides the player the registration reject note if the player was rejected. 1.0 Register Player Player = Name + Age + User Name + Email + Telephone
Player Data The details of the player were saved in Player file as soon as the played registration is accepted. 1.0 Register Player Player file. = Player ID + Name + Age + User Name + Password + Salary + Claim Threshold + Date + Joined Position + Team+ Email + Telephone
Name Description
Claim Details If a player wanted to claim something he sends the details to the system. 45
System Development Methods Origin/Source Destination/Sink Data structure Player 2.0 Manage Player Payroll = Claim ID + Amount + Player ID + Date + Claim Type
CE00321-2
Name Description
Origin/Source Destination/Sink Data structure
Claims Payment Details As the player sends the claim details to the system, it will check whether to approve or not. If the claim detail is approved claim payment details will be updated in claims file. 2.0 Manage Player Payroll Claims file. = Claim ID + Amount + Player ID + Date + Claim Type
Bonus payment details The bonus payment details will requested by the player if need so. Player. 2.0 Manage Player Payroll = Bonus ID + Amount + Player ID + Date + Bonus Type + Match ID
Salary Slip The salary slip will be provided to every player monthly or in any other period of time. 2.0 Manage Player Payroll Player = Salary ID + Amount + Player ID + Date
Payroll Data The process, 2.0 Manage Payroll Data will retrieve the details from the Player file in order to process the payroll. Player file Player = Salary ID + Amount + Player ID + Date
46
System Development Methods Name Description
CE00321-2
Updated Payroll Data The process, 2.0 Manage Payroll Data will retrieve the details from the Player file in order to process the payroll. After the salary paid the Player file will be updated. 2.0 Manage Player Payroll Player file = Salary ID + Amount + Player ID + Date
Salary Payment Details After the process 2.0 the salary payment details will be updated in salary file. 2.0 Manage Player Payroll Salary file = Salary ID + Amount + Player ID + Date
Payment Details Suppliers will be given the payment details as soon they made the apparel supply. 3.0 Handling Purchases Supplier. = Supplier Payment ID + Date of Payment + Invoice No + Total Amount
Good Received Note As soon the goods were received from the Supplier a note was send to supplier. 3.0 Handling Purchases Supplier. = Apparel Detail ID + Apparel ID + Supplier ID + Quantity + Unit Price + Date of Supply + Invoice No
Name Description Origin/Source
Supplier Data The supplier data was retrieved from the supplier table in order to handles the purchases. Supplier file 47
System Development Methods Destination/Sink Data structure
CE00321-2
3.0 Handling Purchases = Supplier ID + Name + Address + Telephone No + Apparel Type + Apparel Description
Payment Details As the purchasing was done the payments which were made to the suppliers will be provided t o the suppliers. 3.0 Handling Purchases Supplier = Supplier ID + Name + Address + Telephone No + Apparel Type + Payment ID + Cost
Payment Details As the purchasing was done the payments which were made to the suppliers will be provided t o the suppliers. 3.0 Handling Purchases Supplier = Supplier ID + Name + Address + Telephone No + Apparel Type + Payment ID + Cost
Supplier Details The details of the supplier will be provided in order to register with the system. Supplier 4.0 Register Supplier = Supplier ID + Name + Address + Telephone No + Apparel Type + Apparel Description
Name Description Origin/Source Destination/Sink
Supplier Registration Confirmation Note The supplier provides the data in order to register. Then the details were validated and if accepted the confirmation note is send. Supplier 4.0 Register Supplier
48
System Development Methods Data structure = Supplier ID + Name + Address + Telephone No
CE00321-2
Contractor Details The details of the contractor will be provided in order to register with the system. Contractor 5.0 Register Contractors = Name + Address + Telephone No + Contract Type
Contractor Data The details of the contractor will be saved in contractor file. 5.0 Register Contractors Contractor = Contractor ID +Name + Address +Telephone No +Contract Type
Contractor Payment Details The contractors will be paid and the payment details will be saved in Made Payments file. 6.0 Handling Maintenance Made Payments = Contractor Payment ID + Date of Payment + Invoice No +Total Amount
Name Description
Contractor Completed Notice As soon the contractor completed his task he will send a notice in order to notify that the maintenance or the specified contract was successfully done. Contractors 6.0 Handle Maintenance = Maintenance Detail ID + Contract ID + Maintenance ID + Cost + Completed Date
49
System Development Methods Name Description Origin/Source Destination/Sink Data structure
CE00321-2
Pending Maintenance Details All the pending maintenance details will be input by a external process in order to carry out the maintenance. Insert Maintenance 6.0 Handle Maintenance = Maintenance ID + Maintenance Type + Location + Maintenance + Level + Description + Status
Apparel Details The details of the apparel which are needed to the player will be given o the system. Player 7.0 Apparel reservation and purchase. = Player apparel ID + Apparel ID + Type + Status + Quantity + Price + Request Date
50
CE00321-2
9.0 Event Model for the Proposed System

Entity Life History
Contractor Payment
Complete Contract
Delete Contract Payment
R1R2 0 0
Reject Payment
Q2
Accept Payment Make Payment
Q1
Salary
Assign Salary
Delete Salary
R1
Reject Salary Payment
0
Pay Salary
0 Q1
51
CE00321-2
Player
Register
Delete Player
R1
Update * Player Details
Resign
0 Q1
Pay Bonus
Pay Claim
Pay Salary
Contract
Create Contract
Complete Contract
Delete Contract
R1
0
Update Contract
Update Maintenance Details
Remove0 Maintenance
0 Q1
If all maintenance removed Q1
52
CE00321-2
Bonus
Finish Match
Calculate Bonus
Pay Bonus
R3R4
Delete Bonus
R1R2
Calculate match Bonus
Calculate Goal Bonus
Accept Match Bonus
Reject match Bonus
Accept goal Bonus
Reject goal Bonus
0 Q2
Q3
Q1
Q4
Claim
Request Claim
Delete Claim
Accept Claim
Reject Claim
Contractor
Register
Delete Contractor
R1
Update * Contractor Details
Register
0 Q1
--
53
CE00321-2
Maintenance
Create Maintenance
Delete Maintenance
R1R2
Update * Maintenance
Complete Maintenance
Cancel Maintenance
Q1
Q2
Apparel Order
Create Apparel Order
Name Title
Sell Apparel
0
Reserve Apparel
0
Reject Order
0 Q1
Cancel Order
0 Q3
Accept Order
Deliver Apparel
Q2
Apparel Order Details
Create Apparel Order
Delete Order Details
0 Reject Apparel Order
Cancel 0 Apparel Order
Delete Order 0 0 Details
Update Order
54
CE00321-2
Apparel
Add New Apparel
Delete Apparel With No Supply 1-4/-
Delete out dated Apparel 1-4/-
Delete Apparel
1-4/-
Add Apparel 1/2
Sell Apparel
Update Apparel Details
1-4/3
1-4/4
Match
Create Match
Delete Match
R1
Update match * details Finish match
Cancel match 0
Q1
Match Detail
Assign Player For matches
Delete Match
R1
Finish Matches
Cancel Match
Q1
Update match details Postpone Match
Q1
55
CE00321-2
Supply Payment
Receive Apparels
Delete Supply Payment
R1R2 0 * Reject Payment Q2

Accept payment Make Payment
Q1
Supplier
Register
Delete Supplier
R1 0
Update Supplier Details
Resign
0 Q1
56
CE00321-2
Purchase order Details
Create Purchase Order
Pay Supplier
Delete Order Detail
R1 * Update Purchase Order Details

Deliver Ordered Apparel
R2
Accept Apparel
Q1
Reject Apparel Resend Apparel
Purchase Order
Create Purchase Order
Pay Supplier
Delete Order
R1 0
R2
Delver Apparel
Accept Order
Q1
Reject order Resend Apparels
57
CE00321-2
Maintenance Details
Create Contract
Delete Contract
R1R2
*
0
Complete Contract
0 Q1
Remain 0 Maintenance
Update Maintenance Details
Q2
58
CE00321-2
10.0 Interactive Screen Design

Intranet Application
Screen Designs Add New Apparels
This is the screen for adding new apparels to the system.
59
System Development Methods Add New Supplier
CE00321-2
This is the screen for adding new suppliers to the system.
60
System Development Methods Add New Apparel Contract
CE00321-2
This is the screen for adding new apparel contracts for the suppliers.
61
System Development Methods Edit Apparel
CE00321-2
This is the screen for editing apparel details.
62
System Development Methods Reject Apparel Request
CE00321-2
This is the screen for rejecting the apparel requests made by the players.
63
System Development Methods Delete Supply
CE00321-2
This is the screen to stop the supply of apparel from a selected supplier.
64
System Development Methods Delete Supplier
CE00321-2
This is the screen to delete suppliers.
65
System Development Methods Delete Apparel
CE00321-2
This is the screen to delete apparel from the system.
66
System Development Methods Issue Apparel
CE00321-2
This is the screen for issuing apparels for the players who have requested items.
67
System Development Methods Report Designs Apparels
CE00321-2
68
System Development Methods Contracts
CE00321-2
69
System Development Methods Player Apparel Reservations
CE00321-2
70
System Development Methods Reservations
CE00321-2
71
System Development Methods Suppliers
CE00321-2
72
System Development Methods Internet Application Home
CE00321-2
73
System Development Methods Players
CE00321-2
74
System Development Methods Apparels
CE00321-2
75
System Development Methods Shopping Cart
CE00321-2
Login
76
System Development Methods Apparel Description
CE00321-2
77
System Development Methods Register Player
CE00321-2
78
System Development Methods Matches
CE00321-2
79
CE00321-2
11.0 Programming Environment
The programming language chosen to be used for the project was ASP.Net with C#. ASP.net allows developing web applications which interacts with a database. Also it supports to implement many functionalities and it consists with many programming tool therefore it enables make the development process faster. (Exforsys 2010)
Advantages, which include: Speed Stability High Security Easiness in learning and using Open Source- can obtain free scripts with required functionality
This also supports XML , use authentication schemes, cache frequently used data and customize application's configuration.( Exforsys 2010)
Since it is free, easy to learn, and works well with several platforms and software programs, it was identified as the most suitable to use for the project.
80
CE00321-2
Reference
Exforsys
(2010),
ASP.NET
with
C#
Training
Launch
[Online],
Available
from:
http://www.exforsys.com/tutorials/asp.net/asp.net-with-csharp-training.html January 2010]
[Accessed: 15
Pressman R., (2001), Software Engineering: A practitioner's Approach, 6th Ed.
Alexandrou (2010), Systems Development Life Cycle (SDLC) [Online] Available from: http://www.mariosalexandrou.com/methodologies/systems-development- life-cycle.asp [Accessed: 02nd June 2010]
Computer Systems Odessa Corporation (2010), Structured Systems Analysis and Design Method (SSADM) with ConceptDraw PRO [Online], Available from: http://www.conceptdraw.com/en/products/cd5/ap_ssadm.php [Accessed: 05th June 2010]
Business
Solutions
(2010),
What
is
SSADM?
[Online],
Available
from:
http://www.selectbs.com/adt/analysis-and-design/what- is-ssadm [Accessed: 30th May 2010]
Stylusinc.com (2008), Stylus Success Stories: Software Development Case Studies [Online], Available from: http://www.stylusinc.com/Common/SuccessStories/index.php [Accessed: 09th June 2010]
81

SDM

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDM

Uploaded by

Copyright:

Available Formats

Submitted By: Charith Devaka Sooriyaarachchi Maheeka Jayasuriya Suhail Jamaldeen CB003344 CB003346 CB00

Submitted To: Ms. Zeenath Hidaya

Module Title and Code: CE00321-2 System Development Methods

Intake Code: HF09B1SE

Assignment Title: Boca Juniors Management System

Date Due: 05th July 2010

System Development Methods

System Development Methods

Asia Pacific Institute of Information Technology

System Development Methods

The objectives of the system were identified as below.

Asia Pacific Institute of Information Technology

Asia Pacific Institute of Information Technology

System Development Methods

2.0 Schedule Planning

Asia Pacific Institute of Information Technology

System Development Methods

Asia Pacific Institute of Information Technology

System Development Methods

Work Load Matrix

80% 70% 40% 100% 10% 20%

23% 45% 40% 40% 90% 66.67%

23% 45% 40% 40% 10% 16.66%

55% 10% 100% 20% 10%

100.00% 33.33% 33.33% 33.33%

Asia Pacific Institute of Information Technology

System Development Methods

3.0 Selection of Methodology

Asia Pacific Institute of Information Technology

Asia Pacific Institute of Information Technology

System Development Methods Prototyping Methodology

(Source: Pressman R., 2003)

Asia Pacific Institute of Information Technology

Asia Pacific Institute of Information Technology

System Development Methods

Asia Pacific Institute of Information Technology

System Development Methods

4.0 Problem Analysis Current System

Asia Pacific Institute of Information Technology

Asia Pacific Institute of Information Technology

System Development Methods

5.0 Overview - Proposed System

Asia Pacific Institute of Information Technology

System Development Methods Players

System Development Methods

Asia Pacific Institute of Information Technology

System Development Methods

System Development Methods

Asia Pacific Institute of Information Technology

System Development Methods

6.0 Process Model for the Proposed System

Player Details Player Registration Details Contractor Registration Confirmation Note

Accept Contract Notice

Bonus payment Details

Claim Payment Details

Boca Juniors Management System (BJMS)

Claim Payment Details

Good Received Note Purchase Order

Pending Maintenance Data

Supplier Supplier Registration Confirmation Note Rejected Supplier Registration Note

Add Apparel System

Match Performance System

Asia Pacific Institute of Information Technology

System Development Methods