Description
The objective of this ppt is about a typical software project and its management.
Software Project Management
S O F TWA R E R EQ UI R EM EN T S P EC I F I C A TI O N ON F E E M A N A G EM EN T
(TO MANAGE FUNDS IN INSTITUTE)
Scope & Objective
?
Purpose
? The objective of this document is to describe the
functional and technical implementation details of the Fee management system being developed with reference of the statement of work.
?
Scope And Objective
? The Objective of this application software is to
manage the Fee payments and Fee dues of an Educational Institution so as to achieve a better and effective control of Fee payments and details.
Use Case Diagram
System
CHECK ACCOUNTS FEE OFFICER PAYMENTS MODES ______________ BY CASH THROUGH BANK
OUTSTANDING FEE _______________ CLASS-WISE OUTSTANDING STUDENT-WISE OUTSTANDING
LOGIN/ REGISTRATION
STUDENT/ PARENT/ NEW USER
RECEIPT GENERATION
DATABASE UPDATION
ADMINISTRATOR ALERT GENERATION
Class Diagram
ADMINISTRATOR/ DATABASE FEE OFFICER -LOGIN ID #PASSWORD -EMAIL ADDRESS -PHONE NUMBER +ADD NEW ACCOUNT() -UPDATE EXISTING() -DELETE EXISTING() -UPDATE FEE() +ISSUE RECEIPTS() -UPDATE STATUS() +VIEW ALERTS() +VIEW PAYMENT HISTORY() * 1 1 1 +NAME +CLASS -TYPES OF FEE -TOTAL FEE PAID -OUTSTANDINGS -DIFFERENT TIME FRAMES -ADD FEE PAID() -REMOVE PENDING FEE() -SHOW ALL FEE DETAILS() +PAYMENT HISTORY()
*
* 1
* * 1
* * N
STUDENT -LOGIN ID -NAME -DATE OF BIRTH -ADMISSION DETAILS -FEE DETAILS -CONTACT INFO -ADDRESS +FEE DUES() +FEE PAID() +RECEIPT ISSUED() +RECEIPT PRINTED() +()
1
*
*
N
*
1
*
N
ALERTS +FEE DUE +TYPE OF FEE DUE +DUE DATE +LATE FEE +SEND TO ADMIN() +SEND TO FEE OFFICER() +SEND TO USER()
PAYMENT -NAME -CLASS -ID No. -PAYMENT DETAILS -OUTSTANDING -PAYMENT UPDATE() -REMOVE FEE FROM DATABASE() +UPDATE DATABASE()
*
*
1
1
*
Deployment Diagram
SERVER DATABASE SERVER
-*
*
DATABSE
WEB SERVER * -* -1 -1 * * SERVER TX
* LOG
-1
ADMINISTRATION * -*
PC PILOT EX
*
-1 * -1..10
PC PILOT -*
PRINTER ASSEMBLY
*
WORK BREAKDOWN STRUCTURE (WBS)
FEE MANAGEMENT SYSTEM
Analysis
• Scope Statement • SRS
Plan
• • • • Scheduling Resource allocation Manpower Resourcing Budgeting
Design
• • • • UML modeling Algorithm Design Interface Design Database Design
Code
• Database Development • Back-end Application Development • User Interface Development
Test
• • • • Unit testing Acceptance Testing Integration Testing System Testing
Deploy
• Trainining of Users • Beta Testing • Delivery
Activity Diagram
STUDENT FEE OFFICER ADMINISTRATOR
FILL REGISTRATION FORM
VERIFY SUBMIT
OUTSTANDING DUES LOG IN
SELECT PAYMENT MODE
PAYS FEES
SUBMIT
UPDATE DATABASE
GENERATE RECEIPTS
Gantt Chart
CPM/ PERT Analysis
CPM/ PERT Analysis (contd.)
CPM/ PERT Analysis (contd.)
Function Point Analysis
Particulars Value (V) Weights (W) VxW
No. of user inputs
No. of user output No. of enquiries No. of files No. of external interface
3
2 3 2 3
4
5 4 10 7
12
10 12 20 21
Total Count Points = 75 * Since our project is of average difficulty so we have used the average weights to calculate the Function points.
Number of files are 2, viz, fee structure and student database. Number of enquiries are 3, viz., Data verification by administrator, modification in fee status, selection of fee structure by students. User inputs are three student, fee-officer and administrator. Number of external interface is 3, viz, student, fee-officer/institute administration, system administrator.
Functional Point Analysis (contd.)
? Complexity multiplier:
We have 12 points of average complexityData communication ? Distributed data processing ? Performance criteria ? End-user efficiency ? Online data entry ? Online data modification ? Online efficiency ? Reusability ? Ease of installation ? Ease of operation ? Portability ? Maintainability
?
So, Complexity Factor = 0.65 + 0.01 x 12 = 0.77 ? No. of Function points = 75 x .77 = 57.75
Estimating
? The project is implemented in JAVA language and
technologies, and hence we assume 1 Function Point = 500 lines of code, So, Total No. of Lines of Code = 57.75 x 500 = 28875. Assuming 75 lines of code is coded daily, ? Then, No. of days = 28875 / 75 = 385. Assuming an additional of 15 days taken, ? Hence total days to complete project = 400
Estimating (contd.)
Assuming average daily cost of Rs. 5000 So, Total cost of the project = 5000 x 400 = 20,00,000 PROJECT COSTS Rs. 20,00,000
doc_101922998.pptx
The objective of this ppt is about a typical software project and its management.
Software Project Management
S O F TWA R E R EQ UI R EM EN T S P EC I F I C A TI O N ON F E E M A N A G EM EN T
(TO MANAGE FUNDS IN INSTITUTE)
Scope & Objective
?
Purpose
? The objective of this document is to describe the
functional and technical implementation details of the Fee management system being developed with reference of the statement of work.
?
Scope And Objective
? The Objective of this application software is to
manage the Fee payments and Fee dues of an Educational Institution so as to achieve a better and effective control of Fee payments and details.
Use Case Diagram
System
CHECK ACCOUNTS FEE OFFICER PAYMENTS MODES ______________ BY CASH THROUGH BANK
OUTSTANDING FEE _______________ CLASS-WISE OUTSTANDING STUDENT-WISE OUTSTANDING
LOGIN/ REGISTRATION
STUDENT/ PARENT/ NEW USER
RECEIPT GENERATION
DATABASE UPDATION
ADMINISTRATOR ALERT GENERATION
Class Diagram
ADMINISTRATOR/ DATABASE FEE OFFICER -LOGIN ID #PASSWORD -EMAIL ADDRESS -PHONE NUMBER +ADD NEW ACCOUNT() -UPDATE EXISTING() -DELETE EXISTING() -UPDATE FEE() +ISSUE RECEIPTS() -UPDATE STATUS() +VIEW ALERTS() +VIEW PAYMENT HISTORY() * 1 1 1 +NAME +CLASS -TYPES OF FEE -TOTAL FEE PAID -OUTSTANDINGS -DIFFERENT TIME FRAMES -ADD FEE PAID() -REMOVE PENDING FEE() -SHOW ALL FEE DETAILS() +PAYMENT HISTORY()
*
* 1
* * 1
* * N
STUDENT -LOGIN ID -NAME -DATE OF BIRTH -ADMISSION DETAILS -FEE DETAILS -CONTACT INFO -ADDRESS +FEE DUES() +FEE PAID() +RECEIPT ISSUED() +RECEIPT PRINTED() +()
1
*
*
N
*
1
*
N
ALERTS +FEE DUE +TYPE OF FEE DUE +DUE DATE +LATE FEE +SEND TO ADMIN() +SEND TO FEE OFFICER() +SEND TO USER()
PAYMENT -NAME -CLASS -ID No. -PAYMENT DETAILS -OUTSTANDING -PAYMENT UPDATE() -REMOVE FEE FROM DATABASE() +UPDATE DATABASE()
*
*
1
1
*
Deployment Diagram
SERVER DATABASE SERVER
-*
*
DATABSE
WEB SERVER * -* -1 -1 * * SERVER TX
* LOG
-1
ADMINISTRATION * -*
PC PILOT EX
*
-1 * -1..10
PC PILOT -*
PRINTER ASSEMBLY
*
WORK BREAKDOWN STRUCTURE (WBS)
FEE MANAGEMENT SYSTEM
Analysis
• Scope Statement • SRS
Plan
• • • • Scheduling Resource allocation Manpower Resourcing Budgeting
Design
• • • • UML modeling Algorithm Design Interface Design Database Design
Code
• Database Development • Back-end Application Development • User Interface Development
Test
• • • • Unit testing Acceptance Testing Integration Testing System Testing
Deploy
• Trainining of Users • Beta Testing • Delivery
Activity Diagram
STUDENT FEE OFFICER ADMINISTRATOR
FILL REGISTRATION FORM
VERIFY SUBMIT
OUTSTANDING DUES LOG IN
SELECT PAYMENT MODE
PAYS FEES
SUBMIT
UPDATE DATABASE
GENERATE RECEIPTS
Gantt Chart
CPM/ PERT Analysis
CPM/ PERT Analysis (contd.)
CPM/ PERT Analysis (contd.)
Function Point Analysis
Particulars Value (V) Weights (W) VxW
No. of user inputs
No. of user output No. of enquiries No. of files No. of external interface
3
2 3 2 3
4
5 4 10 7
12
10 12 20 21
Total Count Points = 75 * Since our project is of average difficulty so we have used the average weights to calculate the Function points.
Number of files are 2, viz, fee structure and student database. Number of enquiries are 3, viz., Data verification by administrator, modification in fee status, selection of fee structure by students. User inputs are three student, fee-officer and administrator. Number of external interface is 3, viz, student, fee-officer/institute administration, system administrator.
Functional Point Analysis (contd.)
? Complexity multiplier:
We have 12 points of average complexityData communication ? Distributed data processing ? Performance criteria ? End-user efficiency ? Online data entry ? Online data modification ? Online efficiency ? Reusability ? Ease of installation ? Ease of operation ? Portability ? Maintainability
?
So, Complexity Factor = 0.65 + 0.01 x 12 = 0.77 ? No. of Function points = 75 x .77 = 57.75
Estimating
? The project is implemented in JAVA language and
technologies, and hence we assume 1 Function Point = 500 lines of code, So, Total No. of Lines of Code = 57.75 x 500 = 28875. Assuming 75 lines of code is coded daily, ? Then, No. of days = 28875 / 75 = 385. Assuming an additional of 15 days taken, ? Hence total days to complete project = 400
Estimating (contd.)
Assuming average daily cost of Rs. 5000 So, Total cost of the project = 5000 x 400 = 20,00,000 PROJECT COSTS Rs. 20,00,000
doc_101922998.pptx