Software Project Planning Example2: A project size of 200 KLOC is to be developed.

Software development team has average

A Software Project is the complete methodology of programming advancement from Project Scheduling experience on similar type of projects. The project schedule is not very tight. Calculate the Effort,
requirement gathering to testing and support, completed by the execution procedures, Project-task scheduling is a significant project planning activity. It comprises deciding which functions development time, average staff size, and productivity of the project.
in a specified period to achieve intended software product. would be taken up when. To schedule the project plan, a software project manager wants to do the
Need of Software Project Management following: Solution: The semidetached mode is the most appropriate mode, keeping in view the size, schedule
Software development is a sort of all new streams in world business, and there's next to and experience of development time.
no involvement in structure programming items. Most programming items are customized i. Identify all the functions required to complete the project.
to accommodate customer's necessities. The most significant is that the underlying technology ii. Break down large functions into small activities. Hence E=3.0(200)1.12=1133.12PM
changes and advances so generally and rapidly that experience of one element may not be Iii. Determine the dependency among various activities. D=2.5(1133.12)0.35=29.3PM
connected to the other one. All such business and ecological imperatives bring risk in software Iv. Establish the most likely size for the time duration required to complete the activities.
development; hence, it is fundamental to manage software projects efficiently v. Allocate resources to activities.
what are the 7 steps of project planning? vi. Plan the beginning and ending dates for different activities.
Step 1: Define your goals and objectives. ... vii. Determine the critical path. A critical way is the group of activities that decide the duration of the
Step 2: Set success metrics. ... project.
Step 3: Clarify stakeholders and roles. ... Comparison of these three types of Projects in COCOMO Model
Step 4: Set your budget. ... Aspects Organic Semidetached Embedded
Step 5: Align on milestones, deliverables, and project dependencies. Project size 2 to 50 KLOC 50-300 KLOC 300 and above KLOC Example of Basic COCOMO Model?
Step 6: Outline your timeline and schedule. ... Complexity Low Medium High Example1: Suppose a project was estimated to be 400 KLOC. Calculate the effort and development
Step 7: Share your communication plan. Team Experience Highly experienced Some experienced Mixed experience time for each of the three model i.e., organic, semi-detached & embedded.
What is Software Testing as well as includes experts
Software testing is a process of identifying the correctness of software inexperienced staff Solution: The basic COCOMO equation takes the form:
by considering its all attributes (Reliability, Scalability, Portability, Environment Flexible, fewer Somewhat flexible, Highly rigorous, Effort=a1*(KLOC) a2 PM
Re-usability, Usability) and evaluating the execution of software components constrains moderate strict requirement Tdev=b1*(efforts)b2 Months
to find the software bugs or errors or defects. constraints Estimated Size of project= 400 KLOC
Type of Software testing Effort Equation E= 2.4(400)1.05 E= 3.04(400)1.12 E= 3.6(400)1.20 (i)Organic Mode
We have various types of testing available in the market, E = 2.4 * (400)1.05 = 1295.31 PM
Example Simple payroll New System Flight control
which are used to test the application or the software. D = 2.5 * (1295.31)0.38=38.07 PM
system interfacing with software
With the help of below image, (ii)Semidetached Mode
existing systems
E = 3.0 * (400)1.12=2462.79 PM
Uses of Cost Estimation D = 2.5 * (2462.79)0.35=38.45 PM
During the planning stage, one needs to choose how many engineers are required for (iii) Embedded Mode
the project and to develop a schedule. In monitoring the project's progress, one needs E = 3.6 * (400)1.20 = 4772.81 PM
to access whether the project is progressing according to the procedure and takes corrective D = 2.5 * (4772.8)0.32 = 38 PM
action, if necessary Agile Model
The meaning of Agile is swift or versatile."Agile process model" refers to a software development
approach based on iterative development. Agile methods break tasks into smaller iterations, or parts
do not directly involve long term planning. The project scope and requirements are laid down at the
beginning of the development process. Plans regarding the number of iterations, the duration and
the scope of each iteration are clearly defined in advance.
1. Requirements gathering, 2.Design the requirements, 3. Construction/ iteration,
4. Testing/ Quality assurance, 5.Deployment, 6.Feedback
Data Flow Diagrams
A Data Flow Diagram (DFD) is a traditional visual representation of the information flows within a
system. A neat and clear DFD can depict the right amount of the system requirement graphically. It
can be manual, automated, or a combination of both.
Example: Compare the Walston-Felix Model with the SEL model on a software development It shows how data enters and leaves the system, what changes the information, and where data is
expected to involve 8 person-years of effort. stored.
The objective of a DFD is to show the scope and boundaries of a system as a whole.
COCOMO Model
Calculate the number of lines of source code that can be produced.
Boehm proposed COCOMO (Constructive Cost Estimation Model) in 1981.COCOMO
Calculate the duration of the development.
is one of the most generally used software estimation models in the world. COCOMO
Calculate the productivity in LOC/PY
predicts the efforts and schedule of a software product based on the size of the software
Calculate the average manning
Types of Projects in the COCOMO Model
Solution:
In the COCOMO model, software projects are categorized into three types based on their complexity,
The amount of manpower involved = 8PY=96persons-months
size, and the development environment. These types are:
(a)Number of lines of source code can be obtained by reversing equation to give:
Organic: A software project is said to be an organic type if the team size required is adequately small,
the problem is well understood and has been solved in the past and also the team members have a
nominal experience regarding the problem. Then
Semi-detached: A software project is said to be a Semi-detached type if the vital characteristics such L (SEL) = (96/1.4)1⁄0.93=94264 LOC
as team size, experience, and knowledge of the various programming environments lie in between L (SEL) = (96/5.2)1⁄0.91=24632 LOC
organic and embedded. The projects classified as Semi-Detached are comparatively less familiar and (b)Duration in months can be calculated by means of equation
difficult to develop compared to the organic ones and require more experience better guidance and D (SEL) = 4.6 (L) 0.26
creativity. Eg: Compilers or different Embedded Systems can be considered Semi-Detached types. = 4.6 (94.264)0.26 = 15 months
Embedded: A software project requiring the highest level of complexity, creativity, and experience D (W-F) = 4.1 L0.36
requirement falls under this category. Such software requires a larger team size than the other two = 4.1 (24.632)0.36 = 13 months
models and also the developers need to be sufficiently experienced and creative to develop such (c) Productivity is the lines of code produced per persons/month (year)
complex models.
Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.
Software Cost Estimation
For any new software project, it is necessary to know how much it will cost to develop and how
Data Flow: A curved line shows the flow of data into or out of a process or data store.
much
development time will it take. These estimates are needed before development is initiated, but how (d)Average manning is the average number of persons required per month in the project
Data Store: A set of parallel lines shows a place for the collection of data items. A data store indicates
is this
that the data is stored which can be used at a later stage or by the other processes in a different
done? Several estimation procedures have been developed and are having the following attributes in
order. The data store can have an element or group of elements.
common.
Purpose of Use Case Diagrams?
The main purpose of a use case diagram is to portray the dynamic aspect of a system. It accumulates
the system's requirement, which includes both internal as well as external influences. It invokes
persons, use cases, and several things that invoke the actors and elements accountable for the
implementation of use case diagrams. It represents how an entity from the external environment
can interact with a part of the system.
Following are the purposes of a use case diagram given below:
 It gathers the system's needs.
 It depicts the external view of the system.
 It recognizes the internal as well as external factors that influence the system.
 It represents the interaction between the actors.
Rules for Data Flow Diagram?
Following are the rules which are needed to keep in mind while drawing a DFD(Data Flow Diagram).
Data can not flow between two entities. –
Data flow must be from entity to a process or a process to an entity. There can be multiple data
flows between one entity and a process.
Data can not flow between two data stores
Data flow must be from data store to a process or a process to an data store. Data flow can occur
from one data store to many process.
Data can not flow directly from an entity to data store –
Data Flow from entity must be processed by a process before going to data store and vice versa.
A process must have atleast one input data flow and one output data flow –
Every process must have input data flow to process the data and an output data flow for the
processed data.
A data store must have atleast one input data flow and one output data flow –
Every data store must have input data flow to store the data and an output data flow for the
retrieved data.
UML Activity Diagram
In UML, the activity diagram is used to demonstrate the flow of control within the system rather than
the implementation. It models the concurrent and sequential activities.

The activity diagram helps in envisioning the workflow from one activity to another. It put emphasis
on the condition of flow and the order in which it occurs. The flow can be sequential, branched, or
concurrent, and to deal with such kinds of flows, the activity diagram has come up with a fork, join,
etc.
When software planner wants to specify resources, they specify it using four characteristics :
 Description of resource
 Resource availability
 Time of resource when it will be available
 Duration of resource availability
Project resources
simply mean resources that are required for successful development and completion of project.
These resources can be capital, people, material, tool, or supplies that are helpful to carry out certain
tasks in project. Without these resources, it is impossible to complete project. In project planning
phase, identification of resources that are required for completion of project and how they will be
allocated is key element and very important task to do. In project management, some resources that
are required are assigned to each task of project to get job done. There are three types of resources
that are
1. People
2. Reusable software components
3. Hardware and software tools

The initial part of project planning is critical as it sets the foundation for the entire project. It typically
includes the following steps:
1. Define prject objectives
2. Indentify Stakeholders
3. Conduct feasibility study
4. Define scope
5. Develop a business case
6. Create a project charter
7. Assemble a team
8. Outline high level timeline
9. Identify risks and assumptions
10. Secure initial approval