Software Project Management
UNIT-2
Lecture-4
Selection of an Appropriate Project Report:
1. Define the Purpose of the Report
Determine the goal of the project report (e.g., academic, business, technical, research).
Identify the key outcomes you want to achieve.
2. Identify the Target Audience
Consider who will be reading the report (e.g., supervisors, investors, stakeholders).
Ensure the report meets their expectations and level of expertise.
3. Select a Relevant Topic
Choose a topic that aligns with your field of interest or organizational goals.
Ensure the topic is feasible, has enough data sources, and is not overly broad or
narrow.
4. Conduct Preliminary Research
Gather background information on potential topics.
Identify available data, resources, and feasibility of research.
5. Determine the Scope of the Report
Define the boundaries of the project (timeline, budget, resources).
Ensure the scope is neither too ambitious nor too limited.
6. Check Data Availability
Ensure sufficient primary or secondary data is available to support analysis.
If required, verify whether surveys, interviews, or case studies are feasible.
7. Analyze Feasibility
Assess whether the project can be completed within available time and resources.
Consider technical, financial, and logistical constraints.
8. Select the Appropriate Format
Decide on the structure (e.g., research-based, analytical, descriptive).
Follow any prescribed guidelines (e.g., APA, IEEE, company format).
9. Evaluate Risk Factors
Identify potential challenges (e.g., lack of data, technical difficulties).
Plan mitigation strategies to address potential issues.
10. Make a Final Selection
Choose the most suitable project report based on all the factors above.
Get approval from relevant authorities (if needed) before proceeding.
Choice of Process Model in Software Project Management
Selecting an appropriate software process model is crucial for the success of a project. The
choice depends on various factors such as project size, complexity, requirements stability,
risk factors, and team expertise. Below are the key considerations and the commonly used
models:
1. Factors Influencing the Choice of Process Model
Project Size – Small, medium, or large-scale projects
Requirements Stability – Fixed or evolving requirements
Risk & Complexity – High-risk projects require iterative approaches
Time Constraints – Whether a quick release is needed
Customer Involvement – Continuous feedback vs. fixed deliverables
Development Team Expertise – Familiarity with different models
Budget & Resources – Availability of funds and technical resources
How to Select the Right Process Model?
If requirements are clear & fixed → Waterfall / V-Model
If requirements may change → Agile / Incremental
If project is high-risk → Spiral
If speed is the priority → RAD / DevOps
If testing is crucial → V-Model
Structured Methods
Structured methods in software project management are systematic approaches that help in
planning, designing, developing, and managing software projects in an organized and
predictable manner. These methods ensure that software development follows a well-defined
process, reducing risks and improving quality.
Key Characteristics of Structured Methods
Process-Driven – Follows a defined sequence of steps
Documentation-Oriented – Requires proper documentation at every phase
Predictable & Repeatable – Provides a consistent way to manage projects
Focus on Risk Management – Identifies and mitigates risks early
Emphasizes Quality Control – Includes reviews, testing, and validation
RAD (Rapid Application Development) Model
RAD is a linear sequential software development process model that emphasizes a concise
development cycle using an element-based construction approach. If the requirements are
well understood and described, and the project scope is a constraint, the RAD process enables
a development team to create a fully functional system within a concise time period.
RAD (Rapid Application Development) is a concept that products can be developed faster
and of higher quality through:
o Gathering requirements using workshops or focus groups
o Prototyping and early, reiterative user testing of designs
o The re-use of software components
o A rigidly paced schedule that refers design improvements to the next product version
o Less formality in reviews and other team communication
The various phases of RAD are as follows:
1.Business Modelling: The information flow among business functions is defined by
answering questions like what data drives the business process, what data is generated, who
generates it, where does the information go, who process it and so on.
2. Data Modelling: The data collected from business modeling is refined into a set of data
objects (entities) that are needed to support the business. The attributes (character of each
entity) are identified, and the relation between these data objects (entities) is defined.
3. Process Modelling: The information object defined in the data modeling phase are
transformed to achieve the data flow necessary to implement a business function. Processing
descriptions are created for adding, modifying, deleting, or retrieving a data object.
4. Application Generation: Automated tools are used to facilitate construction of the
software; even they use the 4th GL techniques.
5. Testing & Turnover: Many of the programming components have already been tested
since RAD emphasis reuse. This reduces the overall testing time. But the new part must be
tested, and all interfaces must be fully exercised.
When to use RAD Model?
o When the system should need to create the project that modularizes in a short span
time (2-3 months).
o When the requirements are well-known.
o When the technical risk is limited.
o When there's a necessity to make a system, which modularized in 2-3 months of
period.
o It should be used only if the budget allows the use of automatic code generating tools.
Advantage of RAD Model
o This model is flexible for change.
o In this model, changes are adoptable.
o Each phase in RAD brings highest priority functionality to the customer.
o It reduced development time.
o It increases the reusability of features.
Disadvantage of RAD Model
o It required highly skilled designers.
o All application is not compatible with RAD.
o For smaller projects, we cannot use the RAD model.
o On the high technical risk, it's not suitable.
o Required user involvement.
Software Project Management
UNIT-2
Lecture-5
