Questions and Answers on SE (UNIT 1)

FAQ on Software Engineering (Unit 1)

Question 1

Discuss the major areas of applications of software.

Software has become an integral part of modern life, with applications in virtually every industry and aspect of daily living. The major areas can be categorized as follows:

Business and Productivity:

This is one of the largest application areas. Software in this category is used to streamline operations, manage resources, and improve efficiency. This includes:

• Enterprise Resource Planning (ERP): Systems that integrate various business processes, such as finance, human resources, and supply chain management.
• Customer Relationship Management (CRM): Software used to manage interactions with current and potential customers.
• Office Automation: Applications like word processors (Microsoft Word), spreadsheets (Excel), and presentation tools (PowerPoint) that are essential for daily office tasks.

Scientific and Engineering:

Software is crucial for research, analysis, and design in scientific and engineering fields.

• CAD/CAM: Computer-Aided Design and Computer-Aided Manufacturing software is used to design and manufacture physical products.
• Simulations: Software is used to model and simulate complex systems, from weather patterns to nuclear reactions.
• Data Analysis: Tools like MATLAB and R are used to analyze large datasets and perform statistical computations.

Embedded Systems and IoT:

This category includes software built into non-computer devices.

• Automotive: Software controls everything from engine management to infotainment systems in modern cars.
• Smart Devices: The software in smart homes, appliances, and wearable technology.
• Robotics: Software is used to program and control robots for manufacturing, exploration, and other tasks.

Question 2

Distinguish between generic and customized software products.  Which one has large share of market and why?

• Generic software products are developed for a wide range of customers with similar needs, while customized software products are created specifically for a single customer to meet their unique requirements.
• Generic software products have a much larger market share than customized software.
• The primary reason is the economies of scale. 
• Generic software can be sold to millions of users, spreading the initial development cost across a massive customer base. 
• This allows for a lower price point, making it accessible to a wider audience, from individuals to small businesses and large corporations. 
• The broad appeal and lower cost lead to a higher volume of sales and, consequently, a larger overall market presence. 
• In contrast, customized software serves a niche market and is typically very expensive, limiting its adoption to organizations that cannot find a suitable generic solution.

Question 3

What are myths in software development? Identify the software myths related to management and practitioners.

• Software myths are common, but often false, beliefs about the software development process. 
• They arise from a lack of knowledge, an outdated understanding of the industry, or unrealistic expectations. 
•  These misconceptions can lead to poor decision-making, project failures, and a great deal of frustration for everyone involved.

Management Myths

• These myths are often held by managers, customers, and other stakeholders who are responsible for the business and strategic side of a project. 
• They stem from a desire for control and predictability in a process that is often complex and unpredictable.

We can assess the quality of the software only after it's running:

• This is false. Quality can and should be evaluated at every stage of the software development life cycle, from requirements analysis to design and coding. 
• Formal technical reviews, for example, can catch errors and flaws early, when they're much easier and cheaper to fix.

Outsourcing is a surefire way to reduce costs:

• While outsourcing can be cost-effective, it introduces new challenges like communication barriers, time zone differences, and potential quality control issues. 
• Without strong management and clear contracts, these issues can lead to unexpected costs and project delays, making the outsourced project more expensive than an in-house one.

Practitioner Myths

• These myths are commonly held by software developers and engineers themselves. 
• They often relate to the day-to-day work of coding and a misunderstanding of the broader software development process.

The job is done once the code is delivered and it runs:

• A practitioner's work is far from over when the code is released. 
• The majority of a software's life cycle is spent in the maintenance phase, which includes fixing bugs, adapting to new environments, and adding new features.

Software development is just about coding:

• This myth oversimplifies the developer's role. 
• In reality, practitioners spend a significant amount of time on non-coding tasks, such as gathering requirements, designing architecture, writing documentation, and testing. 
• Effective software development is a multi-faceted process that requires a range of skills beyond just programming.

The only deliverable in a software project is the final product: 

• This is a dangerous myth. Important deliverable like design documents, test plans, and user manuals are essential for a project's long-term success. 
• Without proper documentation, the software becomes very difficult to maintain and understand for future developers.

Question 4

Explain the concept of Software Engineering and its significance in doing Software Development.

• Software engineering is the systematic, disciplined, and quantifiable approach to the design, development, testing, and maintenance of software. 
• It applies engineering principles to the software creation process to ensure that the final product is reliable, efficient, and meets user requirements.
• Software development is the actual creation of software, which involves tasks like coding, debugging, and testing. 

While software development is a key part of software engineering, it is not the whole picture.

• Software engineering provides the framework and methodology to guide and manage the entire software development life cycle, from initial concept to final delivery and beyond.
• Software engineering is crucial for software development, especially for large, complex projects, because it introduces structure and discipline. 
• Without it, software development can be an unstructured, inefficient, and often chaotic process

Question 5

Define Software Engineering. Is it an art, craft or science? Justify your answer.

• Software Engineering is a systematic, disciplined, and quantifiable approach to the development, operation, and maintenance of software. 
• It applies engineering principles to the creation of software, aiming for the production of high-quality, reliable, and cost-effective software products.
• Software engineering is a science because it relies on fundamental principles and theories. 
• It uses scientific methods to analyze problems, model systems, and predict outcomes. 
• Concepts like algorithms, data structures, and computational complexity are based on mathematical and logical foundations. 
• It involves systematic analysis, experimentation, and the application of proven techniques to ensure predictable and reliable results. 

 

Question 6

State the difference between program and software.  What is the need for documentation in Software Engineering?

• A program is a set of instructions written in a programming language that performs a specific task. 
• Software is a much broader term that includes the program itself, along with all associated documentation, data, and configuration files needed for it to operate correctly.
• Documentation is essential in software engineering for several reasons, as it serves as a form of communication and a record of the project.
• Some of the benefits of documentation in software engineering are as follows:
• Maintenance and Evolution: It helps developers understand the system's design, code structure, and functionality, making it easier to fix bugs, add new features, or update the software over time.
• Knowledge Transfer: It allows new team members to quickly get up to speed on a project without extensive one-on-one training. This is crucial for long-term projects and when team members leave.
• User Support: Documents, such as user manuals and help files, are vital for end-users to understand how to use the software effectively. Without it, the software may be unusable for its intended audience.
• Quality Assurance: Documentation of requirements and design helps in the testing phase by providing a clear reference point for what the software is supposed to do. This ensures that the final product meets the specified requirements.
• Project Management: It provides a historical record of decisions, changes, and project milestones, which is valuable for auditing, project management, and future planning.

Question 7

Analyze the performance of Waterfall Model and its limitations.

• The Waterfall Model is a traditional, linear, and sequential software development process. 
• Like a real waterfall, it flows downward through distinct phases: requirements analysis, system design, implementation (coding), testing, deployment, and maintenance. 
• Software Engineers must complete each phase before they can begin the next, with no overlap between them. 
• This approach is highly structured, easy to understand, and relies on extensive upfront planning.

The Waterfall Model's performance is strongest in specific scenarios, primarily due to its rigid structure.

• Predictability and Control: With all requirements documented and a detailed plan created at the beginning, the project's timeline and budget are highly predictable. This makes it easier for project managers to track progress and for stakeholders to know what to expect and when.
• Clear Documentation and Structure: Each phase has specific deliverable and well-defined milestones. This results in thorough documentation that is easy for new team members to understand and use, which can be particularly useful for long-term maintenance.

While its rigidity is a strength in some cases, it's also the Waterfall Model's biggest weakness in most modern software development environments.

• Lack of Flexibility: This is the most significant limitation. If requirements change or a new need arises after a phase is completed, it's extremely difficult, costly, and time-consuming to go back and make changes. It essentially means starting over or causing major disruptions.
• Late Bug Detection: Testing is a late phase, occurring only after all the code has been written. This means that any design flaws or errors from earlier stages are not discovered until a large amount of work has already been completed, making them difficult and expensive to fix.

Question 8

What are the advantages of iterative development? Compare iterative development with incremental delivery approach.

• Iterative development is an approach to software development where a system is built and refined through repeated cycles, or iterations. 
• Instead of a single, linear process, you start with a simple, incomplete version of the software and then iteratively add features and improve upon it until the final, complete product is ready. 
• This model is highly flexible and well-suited for projects with unclear or changing requirements.

Advantages of Iterative Development

• Early Risk Identification: By developing a working prototype early on, teams can identify and address potential risks and issues (like design flaws or technical challenges) much sooner than in a linear model.
• Flexibility and Adaptability: This approach allows for changes in requirements to be incorporated easily in subsequent iterations. This is critical in dynamic environments where customer feedback or market demands evolve.
• Customer Involvement: Users and stakeholders can provide feedback on a working prototype after each iteration. This continuous feedback loop ensures the final product meets their needs and increases customer satisfaction.
• Faster Time-to-Market: Although the full product isn't released at once, a basic, working version can be delivered quickly, allowing the business to get a product to market and start getting value sooner.
• Improved Quality: With each cycle, the team learns from previous iterations, allowing them to refine the design, fix bugs, and improve the overall quality of the software.

Iterative vs. Incremental Development

While the terms "iterative" and "incremental" are often used together, they represent distinct concepts. The key difference lies in the focus of each cycle: