Professional Documents
Culture Documents
Softengg Da1
Softengg Da1
1. Illustrate briefly about the below given example, explain the importance of Agile process model in - project
development.
Example of Agile software development
Let us assume that a company named Adobe is working on project to come up with a competing product for
Microsoft Word, that provides all the features provided by Microsoft Word and any other features requested
by the marketing team. The final product needs to be ready in 10 months of time. If they decide to use the
traditional waterfall model, then following things will happen:
• At a high level, the project teams would spend 15% of their time on gathering requirements and analysis
(1.5 months)
• 20% of their time on design (2 months)
• 40% on coding (4 months) and unit testing
• 20% on System and Integration testing (2 months).
• At the end of this cycle, the project may also have 2 weeks of User Acceptance testing by marketing teams.
• In this approach, the customer does not get to see the end product until the end of the project, when it
becomes too late to make significant changes.
Agile Principles:
The principles underlying Agile, as outlined in the introduction, prioritize customer satisfaction, adaptability
to change, and continuous delivery. The methodology promotes collaboration, regular customer interactions,
and a flexible response to evolving priorities. Working software is deemed the primary measure of progress,
setting Agile apart from plan-based methods.
Conclusion:
In conclusion, the Agile software development process model proves indispensable in dynamic business
landscapes. Its iterative approach, continuous customer engagement, and adaptability distinguish it as the
preferred methodology over the traditional waterfall model. By ensuring early and frequent delivery of
valuable software and accommodating changes based on evolving requirements, Agile emerges as a
paradigm shift in project management methodologies.
2. Identify and do risk analysis for the E - Vehicle Tracking Using Driver Mobile GPS Tracking using all possible
risk types.
ANSWER –
**Title: Risk Analysis for E-Vehicle Tracking Using Driver Mobile GPS Tracking**
**Introduction:**
Risk management is a critical aspect of project planning and execution. In the context of developing an E-Vehicle
Tracking system utilizing Driver Mobile GPS Tracking, it is imperative to identify, analyze, and respond to
potential risks. This assignment focuses on the risk management planning for this project, aiming to anticipate
challenges, assess their impact, and formulate a comprehensive risk resolution plan.
Risk management is a systematic process involving the identification, analysis, and response to risks throughout
the project lifecycle. A robust risk resolution plan is formulated to address each identified risk factor, analyzing
their potential impact on the project. This plan outlines probable responses that can be implemented to mitigate
or manage these risks as they arise.
The initial step in risk management is to identify potential risk factors associated with the E-Vehicle Tracking
project. These factors may stem from assumptions, constraints, user expectations, or specific project situations.
Effectively managing these risks involves recognizing and documenting them comprehensively.
**Types of Risks:**
1. **Technical Risks:**
- GPS Signal Interference: Unforeseen disruptions to GPS signals may impact accurate vehicle tracking.
- Mobile App Compatibility: Compatibility issues with diverse mobile devices used by drivers.
2. **Operational Risks:**
- Scope Creep: Uncontrolled expansion of project scope impacting timelines and resources.
4. **Security Risks:**
- Data Breach: Unauthorized access to sensitive tracking data compromising user privacy.
- Cyber Attacks: Potential threats to the integrity of the tracking system through hacking attempts.
**Risk Resolution Plan:**
- Mobile App Compatibility: Regularly update and test the mobile app for various devices.
- Driver Compliance: Conduct regular training sessions and establish clear guidelines.
- Cyber Attacks: Regularly update security measures and conduct penetration testing.
**Conclusion:**
Effective risk management is crucial for the success of the E-Vehicle Tracking project. By identifying and
addressing potential risks, the project team can ensure a smoother development process and enhance the overall
reliability and security of the tracking system. Regular monitoring and adaptation of the risk resolution plan
throughout the project's lifecycle are essential to navigate unforeseen challenges successfully.
3. Assume OLA E-Bike company is in need of a Software Product to maintain all its activity in Automated format,
Identify the requirements for the company and explain the functional and non-functional requirements for it.
ANSWER-
**Title: Software Requirements Specification for OLA E-Bike Company**
**1. Introduction:**
The OLA E-Bike Company aims to streamline its operations through the development of a comprehensive
software system. This document outlines the functional and non-functional requirements necessary for the
successful implementation of the software product.
- **Route Planning:**
- Integration with mapping services for efficient route planning.
- Displaying optimal routes and estimated travel times.
- **Payment Integration:**
- Secure payment gateway integration for online transactions.
- Support for multiple payment methods.
- **Maintenance Tracking:**
- System should track and schedule maintenance tasks for each E-Bike.
- Automated alerts for upcoming maintenance.
- **Security:**
- Ensure data encryption for user information and transactions.
- Implement secure coding practices to prevent vulnerabilities.
- **Scalability:**
- The system should scale to accommodate an increasing number of users and E-Bikes.
- Support for concurrent users during peak times.
- **Reliability:**
- The system should be available 99.99% of the time.
- Backup and recovery mechanisms to prevent data loss.
- **Usability:**
- Intuitive user interface for easy navigation.
- Accessibility features for users with disabilities.
- **Performance:**
- Response time for key functions should be under 2 seconds.
- System should handle concurrent bookings without performance degradation.
- **Compliance:**
- The software should adhere to industry standards for data protection and privacy.
- Follow coding standards and best practices.
- **Interoperability:**
- Ensure compatibility with commonly used web browsers and mobile platforms.
- Integration capabilities with third-party services and APIs.
**4. Conclusion:**
This Software Requirements Specification (SRS) provides a detailed overview of the functional and non-
functional requirements for the OLA E-Bike Company's automated software system. Adhering to these
requirements will ensure the successful development and implementation of a robust, secure, and user-friendly
platform to enhance the efficiency of OLA E-Bike operations.
4. Consider the following Function point components and their complexity. If the total degree of influences is
52, Predict the estimated function points.
Function type Estimated count complexity
ELF 2 7
ILF 4 10
EQ 22 4
EO 16 5
EI 24 4
ANSWER –
5. Explain in detail about COCOMO model for software cost estimation. Use it to estimate the effort required to
build software for a simple ATM that produces 12 screens, 10 reports and has 80 software components.
Assume average complexity and average developer maturity. Use application composition model with object
points.
NOTE: Description of each step should be given. Verification of the answers should be highlighted