1. University of South asia
CSE- 629
SOFTWARE Quality Assurance(Sqa)
Lecture 1:
Course Overview
By: Md Rezaul Huda Reza

2. Introduction – WHO? Lecturer: creativereza@yahoo.com
Md Rezaul Huda Reza
Former Lecturer of
Bexley College under University of Greenwich, UK.
Richmond Upon Thames College, UK.
Uxbridge College, UK.
Carshalton College, UK.
Barking College, UK.
Southend Essex College, UK.
Croydon College, UK.
Microsoft Certified Professional in SQL Design

3. introduction – WHAT?
Provide you with an in-depth understanding of the analysis, design and development of large complex systems.
Aims:
To introduce you to the concerns of software quality assurance practice.
To provide you with sufficient knowledge of the various processes, tools and techniques software engineers may employ when developing software with a particular focus on the Object-Oriented approach.
To provide you with an experience of the way techniques are applied in practice.

4. Lectures PLEASE BRING A COPY WITH YOU!!
Then it will not be necessary to copy from the screen.
Do make a note of lecturer comments which are not on the screen.

5. assessment 2 hour written examination in June of 2015 - 30%
Individual Logbook assignment – 20%
On going, reflective, log of experiences and deliverables.
Final Exam: – 40%
Attendance: – 10 %

6. What is software Engineering
“An engineering discipline that is concerned with all aspects of software production from the early stages of systems specification to maintaining the system after it has gone into use”
Overall aim (ideal): Produce software on time and to a budget that satisfies the requirements of the users and provides an efficient solution to a problem at hand!
 SE helps minimise the likelihood of common problems associated with software projects.
Although such an ideal aim is probably impossible to achieve in practice, software engineering helps to minimise the likelihood of common problems associated with software projects.

7. Our Course includes…
Software Quality Assurance Overview with 5Ps Standardization of software quality assurance Software quality program organization

8. Our Course includes…(Cont)
The cost of SQ, inspections, software configuration management Capability Maturity Model (CMM) Role of SQA in software development maturity
Capability Maturity Model, a tool for assessing processes in organizations during software development. 

9. Our Course includes…(Cont)
Software quality assurance CASE tools Software quality assistance metrics Effective methods of information services quality assurance

10. Our Course includes…(Cont)
Statistical methods applied to software quality control Software reliability management Software safety and its relation to software quality assurance

11. 5Ps for SE How we will study SQA.. Process Project Product People
Problem

12. Se Perspectives Resist any narrow frame of reference to SE
An introduction to software engineering from a ‘project’, ‘problem’, ‘process’ and ‘people’ perspective.
Resist any narrow frame of reference to SE
Because SE is…
not only about building a technical artefact to satisfy a given requirement.
not (just....mostly) about hardware and software
BUT…
an organisational phenomenon situated within a context.

13. therefore…We need to expand our vision…
And pay attention to 5 key aspects-
Process - how we do it
Project - the structures we use to manage it
Product - the things we produce
People - lots of them in various roles
Problem - why we started in the first place

14. Processes
Methodological processes which people will follow in order to move from an idea or problem through to a complete piece of software used by people.
A set of activities inter linked and interdependent in time.
Need to choose the process in regards to what we want to emphasize or ignore as well in regards to sequence and degree of linearity.
The process of an IS, can be seen

15. An example of a Process The typical sequence involves the following:
Problem identification
Determination of requirements
Feasibility study to explore possible approaches
System analysis to model detailed requirements
Systems design to work out how requirements are to be met
Development/Programming
problem identification
feasibility study
project set up and planning
requirements specification
systems analysis
design
programming

16. An example of a process.. Testing and Review Training
Release and Putting the system into use (or else IS implementation)
Maintenance and support
This sequence is known as the IS development life cycle and is the one of the oldest processes followed.
It is intended to provide a logical insight into the activities required, rather than setting down an absolute sequence to be followed at all times.

17. The Project
To instantiate a process we need a more formal structure. We need a project.
It is the structures and resources we use to make the development happen.
A project has goals, resources and it provides the framework within which management can be exercised.

18. Where do Projects Come From?
Problems (e.g. something is not working right)
Pressures (e.g. respond to competition, EU regulations etc.)
Opportunities (e.g. sell online and save costs)
User Needs (e.g. need a system to support accounting)
IS Planning (e.g. strategic planning need for a new system to achieve breakthrough)
Acts of faith
Accidents and Politics

19. Project Activities In creating a project we need to define:
Activity view (how):
Organising
Co-ordinating
Controlling
Resource view (who and with what)
Product view (what)
Outcomes view (with consequences)
In creating a project we need to define, how we will do that and therefore the activity view, how we will organize, coordinate and control the project. Furthermore we need to define who will do what and through what means, what sort of product we will like to develop and what kinds of consequences we should expect.

20. The Project Manager Achieve and sustain commitment
Plan activities and achieve a work breakdown into tasks
Estimate effort and cost
Allocate resources to tasks
Monitor milestones and deliverables
Manage risk, sustain quality, respond
Communicate/evaluate progress, problems and results
The role of the project manager therefore will be to:
Achieve and sustain commitment
Plan activities and achieve a work breakdown into tasks
Estimate effort and cost
Allocate resources to tasks
Monitor milestones and deliverables
Manage risk, sustain quality, respond
Communicate/evaluate progress, problems and results

21. The product
The deliverable of a project. Concrete artefact, a thing to be made and delivered along the way.
A program, a database etc.
A viable and feasible information system.
Should be:
Cost effective
Address the real problem
User friendly
Reliable
Secure
Sustainable through time
The deliverables of an information systems development project.
The products might be programs, databases, etc. An information system in product terms may include: hardware, software, documentation, data resources, training materials, knowledge.
The computer base part of an IS needs to be cost effective, address the real problem, be user friendly, be reliable, secure, and sustainable through time. Of course some aspects of the information system cannot be computerized, like cost, convenience, security, politics and the law, etc.

22. THE Product in is Terms May include: hardware and software
documentation and training materials
data resources
formalised 'knowledge‘
informational transformations and outputs
new jobs and new roles for people

23. People
Those who have some interest in the development and in the shape that the final IS product takes.
An Information systems only makes sense if people are there (analysts, designers, customers, managers, problem owners etc.).
Various ways of naming them
Users...or Participants...
Customers.. Clients...
Actors.... Members
Moving on to the people…who are the people?
Those who have an interest in the development and in the shape the IS product takes..

24. What do people want?
Knowledge contract: the skills and knowledge users bring with them to be used and developed.
Psychological contract: to meet their personal interests, social/psychological aspirations.
Efficiency contract: their personal efficiency to be supported by controls and support services.
Task structure contract: seek a set of tasks that meet personal needs for interest, variety and challenge.
Value contract: seek to work within a situation or organization whose values do not contravene their own.
People have their own desires and needs which they bring to a new system. These could be described in terms of:

25. Finally... The Problem
Why did we start to talk about information systems?
To achieve something new, better, different, but what?
What is a Problem?
‘A situation upon which someone may wish to act’

26. Finally... The Problem
Different problems, different people, different process etc…
BUT also….
For the same problem we can choose to address it in different terms, different process, different project, different people, different product

27. WRAPPING IT UP We will study SQA through the 5Ps.
The course will begin by exploring different kinds of processes.
We will then move on to discuss the set of practices which are linked together around a set of beliefs about the way we should design and develop a system (mostly focus on OOAD).

28. Wrapping it up.. Reading for the 5Ps
Most texts have some introductory material framing what they see as the SE domain.
Read a few and contrast their positions.

29. Any question ? ? ?

30. Thank you