App Dev Pre Finals - H1

Software quality

is the degree to which a software product meets the gathered requirements.

_Software quality assurance

is a set of activities that define and assess the adequacy of software process to provide evidence which establishes confidence that the software processes are appropriate for and produce software products of suitable quality for their intended processes.

_Software quality assurance

This is based on the planning and implementation of a series of activities for ensuring quality in the software development process.

Reputation

– Software developers and their organizations rely on this

Software bugs

can have immediate impacts on clients or customers

“technical debt.

Poor quality software tends to be expensive to develop and maintain, which can negatively affect organizations or end up maintaining the software in the longer term. These costs are often referred to as

Software Certification

– The development and use of the software might require some form of certification, which can often require evidence of the application of various quality control and assessment measures.

_Legality

– There may be overriding legal obligations that apply to organizations that use the software.

_Legality

every practicable measure must be taken to demonstrate that the software system does not pose a risk to its users.

_Ethical Codes of Practice

– In cases where a software system is not covered by software certification and legislation, and where its failure is not necessarily business or safety-critical, there can remain moral obligation to the users.

_Ethical Codes of Practice

This implies that software engineers should do whatever is possible to maximize the quality of their software and to prevent it from containing potentially harmful bugs.

Software prototyping

refers to building software application prototypes which displays the functionality of the product under development, but may not actually hold the exact logic of the original software.

Prototype

moves the quality assurance earlier and makes it easier.

_Throwaway Prototyping

– This is a relatively fast method of prototyping that focuses on employing prototypes to generate insights about the software design idea.

_Throwaway Prototyping

The created prototypes on this paradigm are discarded after testing and after obtaining feedback.

_Throwaway Prototyping

This is used in early design stages where the gathered requirements are still unclear.

_Evolutionary Prototyping

– The prototypes on this paradigm are reused after the testing in a way that they are altered according to the test results and then reused in a new test cycle.

_Evolutionary Prototyping

This evolves to become the end product itself.

_Evolutionary Prototyping

This is usually used in late development stages where sufficient insides about principle design decisions exist and the prototype addresses technical and long-term use issues.

Prototypes

can be created in different fidelities

Low-Fidelity Prototyping

– Its role is to check and test the visual appearance and user flows of a software

low-fidelity.

throwaway prototype can be created in

_Paper-Based Prototyping

– This prototyping technique is used to create a prototype based on hand drawings that represent user interfaces of the software.

_Paper-Based Prototyping

This allows developers to explore ideas and refine designs quickly

_wireframe

is a visual representation of a product page that developers can use to arrange pages of user interfaces

_wireframe

are used to create interactive prototypes by linking different wireframes together.

_High-fidelity prototypes

are created when developers have a solid understanding of what they are going to build.

_High-fidelity prototypes

They need to test it with the actual users.