BSA/385 Week 1 Discussion: Software Process And Requirements ✓ Solved

BSA/385 Week 1 Discussion Software Process and Requirement Analysis

Write a 100- to 200-word response to the following:

1. It is mentioned that "Clients often lack appreciation for the complexities inherent in software engineering, particularly regarding the impact of changing requirements." Imagine you are in this situation, what would you do to handle this situation, using knowledge you have learned in software process?

Quality Procedures

Write a 100- to 200-word response to the following question:

2. Explain why it is important to document quality procedures at the beginning of a project rather than later on. In addition, think about 2 advantages and 2 disadvantages of using standards for documentation in each of the software phases.

Software Engineering: Modern Approaches

Write a 100- to 200-word response to the following questions:

3. Give an example of a software application in which the customer is the same as the end user. Give an example in which they are different. In each case, identify the customer and end user.

Write a 100- to 200-word response to the following question:

4. What are three major advantages and disadvantages of describing detailed requirements with unit tests?

5. Explain why a defective requirement could be 100 times more expensive to fix after software is deployed versus being fixed during requirements analysis.

6. Give two advantages and two disadvantages to using standards for documentation of the various software phases.

7. List four of what you consider to be the most important high-level requirements for an application that tracks bar-coded invoices within a company.

8. Describe in your own words the difference between customer wants and customer needs. Provide an example that illustrates the difference.

Paper For Above Instructions

In the realm of software engineering, managing changing requirements is a critical challenge that can impact project success. When faced with clients who lack an understanding of the complexities involved, I would take the initiative to educate them about the software development process. This could involve organizing meetings to explain the potential consequences of requirement changes, using relatable analogies to illustrate how these changes affect timelines and costs. In my experience, clear communication and setting expectations from the outset can significantly mitigate misunderstandings.

Documenting quality procedures at the beginning of a project is essential as it lays the foundation for consistent practices throughout the development cycle. Early documentation ensures that all team members are on the same page, reduces the risk of errors, and promotes accountability within the team. Two advantages of using standards for documentation include improving the overall quality of the documentation, leading to better project outcomes, and facilitating communication among stakeholders. Conversely, two disadvantages may include the potential for documentation to become overly complicated, burdening the development process, and the risk of stifling creativity by adhering strictly to predefined standards.

Consider a software application such as a mobile banking app. In this scenario, the customer (the bank) and the end user (the customer using the app) are different entities. The bank commissions the app to serve its clients, who are the actual end users accessing their accounts. Conversely, in a self-service application like a personal finance management tool, the customer is also the end user, since individuals seeking to manage their finances would be both commissioning and using the software.

Describing detailed requirements with unit tests offers several advantages. Firstly, it enhances communication among developers by providing a clear understanding of what needs to be accomplished. Secondly, it can lead to early detection of issues, saving time and resources. However, there are also disadvantages; crafting unit tests can be time-consuming, and over-reliance on them may lead to neglecting broader integration tests that assess the software’s overall functionality.

The cost implications of fixing defective requirements after deployment can be staggering. Research suggests that the costs associated with rectifying defects can increase exponentially once the software is in production, with estimates indicating it could be 100 times more expensive than addressing those issues during the requirements analysis phase. Early intervention allows for modifications to be made with relative ease, whereas post-deployment fixes may necessitate extensive rework and additional resources, complicating the development process.

In terms of documentation standards, advantages include providing a framework that can enhance the quality and consistency of documentation across various software phases. However, disadvantages might include the potential rise in project overhead and the limitation of flexibility in documentation practices. Each project may benefit from tailored approaches rather than strict adherence to rigid standards.

For an application that tracks bar-coded invoices, some high-level requirements could include:

• The system must enable the scanning of bar-coded invoices using a mobile or stationary device.
• Users must be able to view invoice details easily through a user-friendly interface.
• The application must integrate seamlessly with existing accounting software.
• Data security measures must be implemented to protect sensitive financial information.

Understanding the difference between customer wants and needs is vital for creating effective solutions. Customer wants are often desires that may not be essential for the core functionality of a product, while customer needs represent critical requirements necessary for the product's success. For example, a financial application user might want a colorful and flashy user interface (want), but they need features that allow secure transactions and accurate tracking of finances (need). This distinction can guide developers in prioritizing features and functionalities that drive user satisfaction while ensuring that essential requirements are met.

References

• Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach. McGraw-Hill.
• Sommerville, I. (2016). Software Engineering. Pearson.
• Schmidt, D.C. (2000). The role of software engineering in the design process.
• McConnell, S. (2004). Code Complete: A Practical Handbook of Software Construction. Microsoft Press.
• Kotnour, T. (2000). The Effect of Project Management Practices on the Success of Projects.
• Charette, R. N. (2005). Why Software Fails. IEEE Spectrum.
• Wagner, S. (2019). Agile documentation: how to create lightweight documentation with agile methods.
• Lean, J., & Poppendieck, M. (2003). Lean Software Development: An Agile Toolkit. Addison-Wesley.
• Boehm, B. W. (1988). A Spiral Model of Software Development and Enhancement.
• Fowler, M. (2010). The New Methodology. Martin Fowler.