Method best to study the module
- The lecture have to devided the students into a small group for discussion and Q&A session.
- Lecture have to give a lot off question and ask student to do it infront of the class
- Do some Q&A session at the end of the class.
Suggestion on topics that should be added or dropped from the module.
- There are no suggestion to add or drop in this module.
Suggestion on any other teaching and learning technique to be used using lecture.
- The students must go infront of the class to draw the use cases that included in this module.this can make student more understand the topic.
- The student must read the module before the class started to get some idea.
- At the end of class,the student must submit the task given by lecture and the lecture must take it as extra mark.
All lesson learn
What is Software quality management.
• Adopts a number of management principles that can be used by upper management to guide their organizations towards improved software product performance
• Often call quality management
• to develop a ‘quality culture’ where quality is seen as everyone’s responsibility
Scope of software quality
large complex system
Ø progress and supports continuity of development
smaller system
Ø quality management needs less documentation and should focus on establishing a ‘quality culture’.
What is software quality
An effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it.
An effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it.
Effective process
Usefull product
Adding value
Quality dimension and factors
• Efficiency
Ø The degree to which the software makes optimal use of software resources.
• Usability
Ø The degree to which the software is easy to learn, use, operate, prepare input for and interpret output from.
• Maintainability
Ø The ease with which repair maybe made to the software
• Reliability
Ø The amount of time that the software is available for use
Achieving software quality
• Quality assurance(QA) - establishes the infrastructure that supports solid software engineering methods, rational project management, and quality control actions.
• Quality of control(QC) - action that helps ensure each work products meets its quality goals (e.g., Review design models to ensure that they are complete and consistent).
• Software engineering method - understand the problem to be solved, create a design that conforms to the problems and exhibit characteristics that lead to software that are reliable, efficient, usable, etc.
• Project management techniques - use estimation to verify that delivery dates are achievable, schedule dependencies are understood and conduct risk planning so that problem do not breed chaos
Role of SQA Group
· Prepares an SQA plan for a project
· Participates in the development of the project’s software process description.
· Reviews software engineering activities to verify compliance with the defined software process.
· Audits designated software work products to verify compliance with those defined as part of the software process.
· Ensures that deviations in software work and work products are documented and handled according to a documented procedure.
· Records any noncompliance and reports to senior management
SQA Goal
· Requirements auality
· Design quality
· Code quality
· Quality control effectiveness
Step to perform statistical SQA
Ø Collect and categorize information about software errors and defects.
Ø Trace each error and defect to its underlying cause (e.g., non-conformance to specifications, design error, violation of standards, poor communication with the customer).
Ø Identify vital few causes of defects (20%) by using the Pareto principle (80% of the defects can be traced to 20 percent of all possible causes)
Ø Move to correct the problems that have caused the errors and defects.
Muhammad Hazwan Bin Abu Bakar(IS085737)
No comments:
Post a Comment