(Vila UNIVERSITY Bachelor of Information Technology (Hons) Assignment Cover Sheet Course Code: - EC3306 Course Title: - Software Project Management Test Title:- Assignment-2 Report Due Date: - 9-10-2023 Date Submitted:- 9-10-2023 Lecturer Name: - Mr. Nirdosh Bista To be completed if this is an individual assignment. | declare that this assignment is my work. | have not worked collaboratively, copied from any other student's work or any other source except where due acknowledgment is made explicitly in the text, nor has any part been written for me by another person. Student Name: - Niranjan Sharma Student ID:- 00019449 Signature: Lecturer's Signature: To be completed if this is a group assignment. We declare that this is a group assignment and that no part of this submission has been copied from any other student's work or source except where due acknowledgment is made explicitly in the text, nor has any part been written for us by another person. Student ID Student Name Signature Lecturer's comments: Total Marks: Lecturer's Signature: Feedback for the student: Vie acknowledged receiving feedback from the lecturer on this assignment. Student's Signature: Extension certification: This assignment has been given an extension and is now due on Lecturer’s Signature:Table of Contents Introduction Gantt Chart .. Network Analysis Network Diagram... Data flow Diagram Function Point Analysis. COCOMO basic model .. COCOMO intermediate mode .. Effort Cost. Distribution by effort Distribution by Calendar. Hardware/Software/Other Cost Total Cost Justification/Rationale .. Conclusion Acknowledgement. References ..Introduction: This is the second assignment in software project management. This assignment focuses on software cost and timeline estimations. Estimating software costs and timelines is a critical component of project management. Itentails estimating the resources, time, and expenses needed to complete a software project within the set timetable and spending The cost assessment models are available for the COCOMO model, Checkpoint, ESTIMACS, SLIM, and Knowledge Plan. The COCOMO model, on which | will work for this project, is one of the most accessible and well-documented cost estimation models available. The project manager, architecture, development, and test teams executing the task should establish and support a robust software cost estimate. In this assessment report, | will present a thorough work plan for predicting software costs and schedules. I'l go through numerous cost estimation models and methodologies and advise on how to produce reliable estimates. | will also go through recommended practices for project estimation and planning for change requests. Let us begin our task with page number four. (Eby, no date) The Examination Seat Plan Management Web Application Project is a large-scale software development project that aims to simplify the process of planning and maintaining examination seating arrangements. This project includes several tasks critical to its success, including project planning, requirements gathering, system design, development, testing, documentation, training, deployment, post-deployment evaluation, and project closure. This report will look at the project's projected length, critical path, cost estimation, function point analysis, and hardware/software needs. We will defend our choices and assumptions, provide a justification for our calculations, and conclude with a thorough grasp of project planning and execution.Gantt Chart: - fj itn feauemen gates [ten desig fctamene fami [reg a fst deoyentevew frsieccosze 1 2075 D6, 2017 uta 3 De 707 eta 203 bee, 207 oss 20 eric ama ae ae or 205 9 fo, 2023 Dect, 207| [1,205 [Dec 207| fo. 203| [Deco 207 fox, 203 bee, 207| fo 2225 loa [oss na nav 25 [SETNetwork Analysis: Description The followingactivities are included in the Examination Seat Plan Management Web Application Project, which consists of 10 activities: Activities Preceding Optimistic Most Likely Pessimistic Activity Duration Duration Duration 1) ) 1) Project Initiation - 4 5 12 Requirements - 1 15 5 Gathering System Design A 2 3 4 Development A 3 4 " Testing A 2 3 4 Documenting c 15 2 25 Training D 15 3 45 Deployment BE 25 35 75 Post-Deployment H 15 2 25 Review Project Closure FGI 1 2 3The provided project's network is depicted below. Network Diagram: Fig. 1.0- Network Diagram From the above Network diagram, we can see that | have calculated the Expected duration, whose formula is ie. T= T+ 41+ T, Also, From the above Network diagram, we can see that | have also calculated the Forward Pass Method and the backward pass method.Let us see a tabular representation of the expected duration, which is as follows: Activities Time Estimate (Weeks) Preceding | Optimistic | Most Likely | Pessimistic | Expected Activity Duration | Duration | Duration | Duration (Tr) (T,) 1) Project Initiation - 4 5 12 6 Requirements - 1 15 5 2 Gathering System Design A 2 3 4 3 Development A 3 4 " 5 Testing A 2 3 4 3 Documenting c 15 2 25 2 Training D 15 3 45 3 Deployment BE 25 35 75 4 Post- H 15 2 25 2 Deployment Review Project Closure FG, 1 2 3 2Also, let us see a tabular representation of the Forward Pass Method and the backward pass method Time [Earliest and Latest] are calculated, which are as follows: Forward Pass Method Backward Pass Method E=0 E=E+t,=0+6=6 E=E+t.=6+3=9 E =B+t.=6+5=11 E =E4+t.-944=13 E =max(E+tyE+tsE+td max [9+2; 11+3; 13+2] = 15 E =E+t. 5+2=17 min (9 133 25)=6 L=bL-tu=134=9 L=L-t.=15-2=13 L=L-t.=15-3=12 L=L-t,=15-2=13 L=B-t.= 172515 L 7 Finally, as we can see, there are two critical paths along which E - Values & L- Values are the same But the longest network of the critical network is known as the critical path Hence, the Critical Path is 1-2-3-6-7-8 and the expected length or Duration of the critical path is 6+3+4+2+2 = 17 Weeks. Duratio Critical Path = AE-H4-J 7 weeks:Data Flow Diagram (DFD): ay ees < Si) 5 a ‘ie | aa RO Sy No) = an sean no / Se Schedule Updated Schedule no lanage Exam >/ (ng Schedule \ Sey i‘ cost 7) Fig. 1.1 - Data Flow DiagramFunction Point Analysis: Functional | Weighting Factor Weighting Factor Weighting Factor Unit (Low) (Average) (High) El 3 4 6 EO 4 5 7 EQ 3 4 6 ILE 7 10 15 EIF 5 7 10 From Data Flow Diagram (DFD) External Input (El) =4 External Output (EO) External Enquiry (EQ) =1 Internal Logic File (ILF) =3 External Interface File (EIF) =0 After recognizing the function point analysis from the DED, we can now represent it in tabular form, We also select a weighting factor from the table above. Function Unit Count Weighting Factor | Count * Weighting (Average) Factor El 4 4 16 EO 1 5 5 EQ 1 4 4 IF 3 10 30 EF 0 7 0 Unadjusted Function Points (UFP) 55 10We can utilize the data from the above table to calculate the Complexity Adjustment Factor (CAF) and Function Points (FP) for the specified Unadjusted Function Points (UFP) using an Average Weighting Factor. We know that, Xfi = (4 x Count of External Inputs) + (5 x Count of External Outputs) + (4 x Count of Internal Logical Files) + (10 x Count of External Interface Files) + (7 x Count of External Inquiries) Now, Xfi = (4x 4) + (5x 1) + (4x3) + (10x 0) + (7x1) Therefore, XFI= 40 Again, Calculating complexity adjustment factor (CAF) We know that, CAF = 0.65 + (0.01 x Xfi) We get, CAF = 0.65 + (0.01 x 40) Therefore, CAF = 1.05 Finally, Calculating function point (FP) We know that, FP =UPF x CAF We get, FP =55x 1.05 Therefore, the answer is 57.75 FP uCOCOMO Basic Model LOC/KDSI/Selected Mode/Rationale/effort/calendar/staffing This technique is the simplest and offers basic estimations based on the number of lines of code (LOC) in the software project. Software al a2 bI b2 Projects Organic 24 1.05 25 0.38 Semi-detached [3 12 25 0.35 Embedded 36 12 25 0:32 Since 1FP = 60LOC We've already identified our function point, therefore 57.75FP = 57.75 x 60 = 3465LOC Since, 1KLOC is 1000LOC Therefore, 3465 / 1000 = 3.465KLOC The software project is organic because the size ofthe code falls between 2-50KLOC Now finding Effort(€) We know that, 1. Effort(E) = a1 x (KLOC)a2 24x 3.465% 1.05 Therefore, Effort (E) =8.849 12Rationale: For effort estimate, | utilized the COCOMO formula using the constants "al" and "a2." These variables’ values are crucial since they define the form of the effort curve. My selection of "a1" (2.4) and "a2" (1.05) indicates an Organic development mode, which depicts an initially complicated project with a somewhat steady growth environment. 2. Development Time (Toe) = b1 x (Effort)Ab2 = 2.2x8,84900.38 Therefore, Development Time = 5.037 Months Rationale: | calculated the development time using the COCOMO formula, which takes into account effort and the constants "b1" and "b2." My selection of "b1" (2.2) and "b2" (0.38) corresponds to the development mode of choice (Organic) and shows the ratio between effort and development time. 3, Staffing = E / Toev = 8.849 / 5.037 Therefore, Staffing = 1.756 Rationale: Effort (E) divided by Development Time (TDev) equals staffing. This computation determines the number of team members needed to execute the project within the time range selected. In my situation, the predicted team size is roughly 1.756 team members, implying that a small team is required to execute the project within the specified period. 4, Productivity = KLOC / Effort 3.465 / 8.849 13Therefore, Productivity = 0.391KLOC/PM [KLOC per staff months] Rationale: Productivity is expressed in KLOC per person-month (KLOC/PM) by dividing the project size (KLOC) by the effort (E). In this case, the computed productivity is roughly 0.391 KLOC/PM, reflecting the development process's efficiency in terms of code generated per unit of labor. 5. Calendar (Duration) = Toev-+ Overheads Overheads involve time spent on non-development activities like as planning, testing, and documentation. Let us assume that the overhead time is one month for this calculation: Calendar (Duration) = 5.037 months + 1 month = 6.037 months Therefore, the approximate calendar or project time for this software development project is 6.037 months. Rationale: To account for non-development tasks, | used a normal overhead time of one month. This extra time contributes to a more realistic project timetable by ensuring that the project's duration covers planning, testing, and other critical duties. Development Mode: Based on the constants and values given, I've picked the Organic development mode, which corresponds to the project's moderate complexity and reasonably steady environment. 14COCOMO Intermediate Model: The COCOMO (Constructive Cost Model) Intermediate mode is a software cost estimation model that aids in determining the effort, time, and staffing required for a software development project. It is more accurate and comprehensive than the Basic COCOMO model and takes a larger range of factors into account that may have an impact on project outcomes. Let us see by doing mathematical solution. Software al a2 bt b2 Projects Organic 32 1.05 25 0.38 Semi-detached [3 12 25 0.35 Embedded 28 12 25 0.32 Let us choose and calculate the Effort adjustment factor based on the following data. Cost Driver Priority Values Required Reliability High 115 Main storage constraints Extra High 1.56 Product Complexity Normal 1.00 Database Size Low 0.94 Now to find effort adjustment factor (EAF) we know that, EAF = Required Reliability x Main storage constraints x Product complexity x Database size Therefore, EAF => 1.68636 15Now, its time to calculate Effort, Development time and Staffing. For, Effort (E) =a x KLOC * a2 X EAF = 3.2 x 3.465 4 1.05 x 1.686 Therefore, Effort (E) => 19.892 PM Again for, 1 x effort *b2 Development Time (Toes =2.5x 19.892 4 0.38 Therefore, Development Time (Tbe.) => 7.78 Months Finally for, Staffing= Effort / Development Time = 19.892 /7.78 Therefore, Staffing => 2.55 (Rounded up to 3 Persons) Rationale: About 19.892person-months of effort are required, according to the projection. An estimated 7.78 months will pass throughout the development phase. It is recommended to staff the project with roughly 2.55 individuals (rounded up to 3 people) in order to finish it within this time limit. 16Effort Cost: The word "effort cost" in the context of software development or project management refers to the. monetary cost associated with the employees required to complete a project. It lists the labor costs, which cover salaries, wages, benefits, and any other expenses related to the project's employees. To calculate effort cost we have, Effort cost= Toa* (cost of the company) Here. From the earlier mentioned COCOMO intermediate model, we learned that it is necessary of 3 Employees who will work there for 7.78 months from now. The following is an assumption of the staff members necessary salaries. Staff Salary (Per month in RS) Designer 50000 Project Manager 65000 Software Developer 68000 Project Analyst 44000 The mean salary for the staff => 50000 + 65000 + 68000 + 44000 Therefore, total amount is RS. 1'94'000 Now for the Effort Cost We know that, Effort Cost = The” £ (cost of the company) =7.78x 194000 Therefore, Effort cost => 1509320 7Distribution by effort Factors Concept | Inception | Elaboration | Construction] Release | Presentation Effort 20% 17% 13% 20% 25% 5% Schedule 15%. 25% 30% 10% 15% 5% Schedule | 15%*7.78 | 25%*7.78 | 30%*7.78 | 10%*7.78 |15%*7.78 | 5%*7.78 [Months] 1.167 1.945 2.334 0.778 1.167 0.389 Months Months Months Months Months Months 18Distribution by calendar: Activities Calendar Month Time Period Performed by Project Initiation 1Oct- 20" Oct 1 week Project Manager Requirements 1Oct- 14" Oct 2weeks Project Analyst Gathering System Design 14" Oct 5!" Nov 3weeks Designer Development SNov-18"Nov 2Weeks Software engineer Testing 18" Nov - 24"Nov 1 week Software Developer Documenting 24% Nov-1*Dec 1 week Stake Holders Training 1 Dec-7"Dec 1 week Project Team Deployment 7 Dec- 14" Dec 1 week Software Deployer Post-Deployment 14 Dec - 20"Dec 1 week Software Deployer Review Project Closure 20" Dec- 26"Dec 1 week Project Manager 19Hardware/Software Cost/Other Cost: Server (Cloud Hosting - AWS) Type RAM Storage Data Transfer Price 3. medium 4GB min 100GB min 1TB per month 2'40'000 User Tools Minimum Recommended Price Requirements Requirements Operating System Windows 7 Windows 10/11 20000 MacOS Mojave MacOS Big Sur or above Libraries / APIs Authentication Data Visualization | 5000 Memory, 4GB 8GB or above 8000 Hard Drive 128GB 256GB or above 14000 Browser Chromium based Chromium based Open source Processor Intel i3 10" Gen or Intel iS 11" Gen or 16000 Michip above & M1 chip or above Total 63'000 Total cost for a single client is RS. 63000 Now, Total cost [for 3 clients/developers per 8 workstations] = 15'12'000 We also have total cost for server = 2'40'000 Therefore, Hardware/software/other cost = RS [15'12'000 + 2'40'000] = RS. 17’52'000 20Total Cost: the sum of the project's costs, taking into account the price of the required hardware, software, and other items as well as labor, effort, and administrative and software operating costs. Particulars Costs Software/Hardware/Other costs 1752000 Effort Cost 1509320 Administrative and other operational cost.__| 230000 (Assumption) Gross cost 3491320 Profit Margin (15% of gross cost) 523698 Total Cost 75,06,338 The total cost for the project is 75,06,338. [Seventy-five lakh six thousand three hundred and thirty-eight] 21Justification/Rational Finally, this study examined the Examination Seat Plan Management Web Application Project in full. By analyzing the expected time, essential route, function points, effort, manpower, and associated expenditures, Ideveloped a framework for successful project planning and management. The critical path analysis aids in identifying the most time-sensitive activities for the project and ensuring that they are managed properly in order to meet the project's deadline, The function point analysis provides insight into the program's functional complexity, which assists in resource allocation and project scheduling. Estimating effort, manpower, and costs enables project managers to appropriately allocate resources and prepare budgets. Using a rational and data-driven approach, this report provides a solid foundation for the project's effective implementation. Overall, this thorough assessment and planning will serve as a guide for the project team, ensuring that the Examination Seat Plan Management Web Application Project is finished effectively, efficiently, and on time. 22Conclusion: Finally, this paper presents a comprehensive overview of the Exam Seat Plan Management Web Application Project. By doing exhaustive estimations of projected time, critical path analysis, function points, effort, staffing, and related expenditures, | have built a solid foundation for complete project planning and management.Furthermore, | used industry-standard diagramming tools, such as Microsoft Visio or Lucid chart, to develop the Data Flow Diagram (DFD), which helped my project planning, In the future, my evaluation will pave the way for additional work, such as improving the user experience, creating a mobile application, investigating integration possibilities with other educational systems, strengthening security measures, incorporating machine learning for optimization, and considering scalability for the needs of larger educational institutions. Ultimately, this comprehensive assessment and planning report will serve as a guiding beacon for the project team, ensuring that the Examination Seat Plan Management Web Application Project is completed efficiently, on budget, and on time, while leaving room for exciting future enhancements and advancements. 23Acknowledgment: The success and outcome of this assignment were likely due to my work in this course. | am incredibly privileged to have gotten this along with my assignment report. | appreciate and thank Mr. Nirdosh Bista for granting me the opportunity to do the assignment report activity and providing me with all the support | needed to finish the assignment correctly. | am really thankful to him for providing excellent support and guidance despite his busy schedule. References: Fingent Technology. (2020). Function Point Analysis - Introduction and Fundamentals. [online] Available at: https://www-fingent.com/blog/function-point-analysis-introduction-and- fundamentals/. EDUCBA. (2020). COCOMO Model | Types of COCOMO Model | Pros and Cons [online] Available at: https://www.educba.com/cocomo-model/. Educative: Interactive Courses for Software Developers. (n.d.). What is the COCOMO model?{online] Available at: https://www.educative.io/answers/what-is-the-cocomo-model. Lucidchart (2017). What is a Data Flow Diagram | Lucidchart [online] Lucidchart.com. Available at: https://www lucidchart.com/pages/data-flow-diagram. Teamgantt (2019). What is a Gantt Chart? Gantt Definitions & Uses | TeamGantt [online] Teamgantt.com. Available at: https://www.teamgantt.com/whatis-a-gantt-chart. 24