Ch2 Flashcards
What is the description of programs when talking about software and what is an example about them
It is the actual source code and files that do procedures and computations
Ex: python scripts , Java, compiled excutables
What is the description of prosedures when talking about software and what is an example about them
Operational stuff required to run, install, maintain and use the sw efficiently
Example:install guides, configuration settings ,SOPs
What does SOPs stand for
Standard operational procedures, they are step by step explanation of how to do a specific task
What is the description of documents when talking about software and what is an example about them
All the written materials that explain the files, functions,design, and usage of sw
Example: design document, user manual, API documentation
What does API stand for
Application programming Interface
Rules for programs to interface with each other
What is the description of Data needed for operation when talking about software and what is an example about them
Data that is needed by the software like database records, logs, user preferences and configrations
What do configrations stand for?
They are rules settings parameters talk about how the software operates
What does SQA include?
It includes making sure that all the phases in the development procces are in good quality
From data
To documentation of the requirements
And codes
And others
What is SQA
It is monitoring the software processes (activities) and methods
Ensuring they have proper quality
Not the software itself yet the process and methods used in making that software
Can a software that worked properly for a period of time for a specific organization suddenly changed (quality )and have failures?
Yes it is and the reason for that is that the software may be tested or made to work for a specific period of time, or work probably with certain amount of users, libraries used may be out of date of updates or any other characteristics, so they software characteristics may cause such failure.
Is it possible to have different user experiences (some face failures and some don’t) in the same software?
Yes it is and the reason for that is that the software may be tested or made to work for a specific period of time, or work probably with certain amount of users, libraries used may be out of date of updates or any other characteristics, so they software characteristics may cause such failure.
Simply different between error , fault, and failure
Error, made by developer and not found so it evolves to fault
Fault aka bug aka defect is when a reviewer or tester find the mistake , but when it is not fixed and deployed either to the end user or internally it becomes a failure
Failure, it is discovered by end user of tester (in staging deployment)
What is an error
Sections of the code that are partially or totally incorrect, may be in syntax or logic
And it is made by a human (analytics, programmers, another member in the team)
What is a fault , what are other names to it
A fault is also called bug or defect
They are errors that are not found by humans but found by reviewers or tester.
They cause incorrect functioning of the software.
What is a failure
When a fault is not discovered and the software is activated, after the run or deployment.
So the root of any failure is an error not found and made by human
Do all faults end up as failures?
No, it may be handled before deployment, same goes will errors and faults
What happens when the reviewers or tester find the fault?
They return it to the author (developer) to fix it
Why is it better for a failure to be discovered by the tester in staging deployment not user in actual depolyment
Because if user finds it it will affect the company and the development team
If the tester finds it , it will be returned to the developer and correct it
When requirements are not met but the code logic is correct what happens
It is either discovered by the reviewer that the requirement is not right and call it a defect
Or after deployment it is discovered and called failure
What do software errors cause?
They cause faults and possibly failures , so bad quality of the software
What are the forms of sw errors
They must all be human mistakes
In code (syntax,logic)
In documentation (missing details, wrong instructions)
In data (bad database)
What are the causes of defects?
Normal causes
Environmental causes
What are the normal causes for defects
Human errors
Code errors
Design flaws
Requirements issues
Insufficient testing
Talk about requirement issues in normal defects causing
When the requirements are ambiguous or incomplete
*This will lead to confusion and then the wrong approach will be taken (wrong implementation)
(The system should be fast) is ambiguous! How fast?
*the requirements are spelled wrong, causing misunderstanding, which will cause reworking and time missing.
Changing Requirements
*when there are a lot of changes happening, there might be mistakes.
*it becomes harder to work on the project when there is constant changes.
Both of these reasons will cause requirements issues
Talk about design flaws issues in normal defects causing
Poor design or system architecture
*when the design in bad and there are flaws, it will give bad performance (slow system)
And hard to maintain system (update or fix), scalability problems,security problems (easy attacks because of bad architecture), hard to develop in future.
*insufficient design review, if it is not reviewed it will have flaws, and major design problems may not be noticed hence causing problems later on.
Talk about coding errors in normal defects causing
*lack of coding standards, not documentation, conventions, makes code inconsistent and lead to faults and maintenance harder.
Whiteout the standards checklist, developer will write a code that is hard to understand and debug.
*insufficient code review, if code is not reviewed it will correctly it will have mistakes that hard to notice and other defects.
Talk about testing gaps issues in normal defects causing
*inadequate testing coverage, this is also called shallow testing, testing on the surface not deeply ,will cause deep and severe faults not to appear, shallow testing will not cover extreme and big confditions.
*lack of automated testing:manual testing may not give right results and may not cover all cases .
Talk about human factors issues in normal defects causing
*developer inexperience, fresh developer find it hard to work with top programs since they don’t have the skills and knowledge required. They may not know the best practices which makes errors.
*Communication breakdown: lack of communication causes misunderstanding and confusion and bad instructing between team members.
How to prevent normal defect causes?
*better requirements gathering : clear and detailed docs, and stakeholder involvment
*put design practices: do reviews and make standards.
*coding standards:make good and regular code review, and make guideline (conventions) for coding
*strengthen testing : increase test coverage, make automated testing
Talk about environmental causes of defects
They are caused by the environment of the software (external conditions)
*hardware failure (server crashes)
*When software interfaces with other software or API o pr library and they fail
*network problems and infrastructure problems.
*security threats (cyber attacks) may also be caused from bad architecture design in the first place
*actual environment factors, like power outages and disasters.
What is software quality definition according to IEEE
.a degree to which the whole system or component or process meets specific requirements (in other words user or customer needs or expectations)
what is software quality according pressmans definition
.the software must conforms to the explicit performance and functional requirements, and documentation standards coming from the user or other external areas such as industry of company.
.implicit stuff and characteristics coming from the developer himself, stuff that he does because they are expected from a professional developer.
what are the key aspects of pressmans defenition of software
.explicit performance and functional requirements .
.explicit documentation standards.
.implicit characteristics
one of the key aspects of pressmans definition of software is explicit performance and functional requirements , explain
the software must do the explicit function requirements (what should the software do) and the explicit performance requirements (how well should it do it ).
one of the key aspects of pressmans definition of software is explicit documentation standards , explain
the developer must go by standards given from the industry, coding guidelines and best practices coming from the company
one of the key aspects of pressmans definition of software is implicit characteristics , explain
stuff that the developer should do without the user requiring them, they help with meeting the explicit requirements, such as making good reliability, maintainability , usability
give the SQA definition according to IEEE
.it is a planned and systematic pattern on all the needed actions. to provide adequate confidence that an item or product conforms to its technical requirements
.it is also a set of activities designed to evaluate the process by which the products are developed or manufactured
is SQA the same is quality control?
no they are not
is the IEEE definition of SQA complete? what is it missing?
it is not complete
it is missing
.maintenance
.budget
.timeline issues
What should be added to the IEEE definition of SQA, explain them
maintenance, the SQA should not only focus on the development process it should focus on cover the long years of service after delivering the software.
.budget and timeline issues, SQA should not only be limited to the technical requirements of the product , it should take these stuff in consideration
what is the full SQA (expanded definition)?
.it is a systemic or planned pattern of actions that are used to provide adequate confidence that a specific software development and maintenance both conforms to its technical functional requirements, along with the management requirements, such as keeping track of the schedule and operate within the budget confines ( حدود).
.
what is quality contorl?
it is a set of activities that are designed to evaluate a manufactured or developed product (the products are read for shipment) it is done before shipping it to the end user
what is the objective of quality control?
withholding( حجب) any product the does not qualify to go to the end user
how is QC related to SQA
.quality control is just a part of SAQ, so it is just a part of the large range of activities done in SQA to ensure the software quality.
compare between SQA and QC with definition
.SQA is a set of activities that are, methodologies and standards that ensures the the software will meet the required quality standards.
.QC it is the process the activities the methodologies that are used to check if the developed product met the required standard
SQA vs SQC (target comparison)
.SQA focus on developing the methodologies and activities used to see if the product will meet the required standards.
.SQC will focus of improving the actual product by finding bugs and weaknesses.
SQA VS SQC ( orientation comparison)
SQA is process oriented
SCQ product orientated.
SQA vs SQC (nature of the process)
SQA is a preventive process, so it develops activities and methodologies to prevent bugs
SQC is a corrective process, focus on correcting the product by identifying fixing bugs.
SQA vs SQC ( in terms of verification and validation)
SQA is a verification process that verify that you are doing the right things in the right manners (you are using the right processes of activities )
SQC is a validation process that validates that the product meets the requirements
SQA VS SQC ( who does them)
SQA all person involved in the project from requirements to maintenance.
SQC either the testing team or the software quality control inspector
when talking about SQA , all the persons involved in the project are responsible for doing SQA , who gives them the standards to work on?
the project lead or manager
give an example on the activities used in SQA and SQC
SQA
. checklist
.process standards
.process documentation and audit
SQC
.testing process
.peer review
.inspection
what is performance requirements?
they are the same as non functional requirements
