Module 8

Software Evolution

Method best to study the module

• group discussion
• use mindmap
• do open session slot to Q&A

Suggestion on any other teaching and learning technique to be used using lecture.

• Student should read the notes before the lecturer begin the lecture.
• Do some revision at home to create some idea how the system work.
• At the end of the class,student should had a meeting in their small group to get more clearer about the topic.
• At the end of the lecture,student should do some Q&A with the lecturer n student.

All the lesson learnt

• Software Maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes

• Including :               1.Correcting defects

  2.Adapting application to a changing 

                        business environment

                  3.Implementing enhancement at the request of stakeholders

                           4.Supporting users as they integrate an application into their personal and business workflow

• Lehman 's Law

• Who Perform Maintenence?

1. seperate maintenence team
2. part of development team

• Reengineering

model of BPR

1. business process re-engineering model
2.  re-engineering
3. inventory analysis
4. document restructuring
5. reverse engineering
6. code structuring
7. data structuring
8. forward engineering

Muhammad Rijaluddin Bin Mohd Rusli (IS08573

 

module 7

software Quality Management

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.

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)

AGAIN, JUST FOR FUN

INGIN MENCARI JODOH???

KAMI SEDIA MEMBANTU

click picture below

JUST FOR FUN

NAK TENGOK MOVIE SANGAT ??

CLICK JA GAMBAR BAWAH NI

Module 6

Software Verification & Validation

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 the lesson learnt

Strategic approach to software testing

•           Verification and validation
•           Organization of software testing
•          Criteria for completing of testing
•          Software testing strategy

                                 i.            Unit testing

                                ii.            Integration testing

                              iii.            Validation testing

                               iv.            System testing

Unit testing.

1. Ø  Interface
2. Ø  Local data structure
3. Ø  Boundary conditional
4. Ø  Independent path
5. Ø  Error handling path

Integration testing

1. Ø  Bottom up integration
2. Ø  Top-down integration
3. Ø  Regression testing
4. Ø  Smoke testing

Validation testing

• Ø  Focuses on uncovering errors at the software requirements level.
• Ø  SRS might contain a ‘Validation Criteria’ that forms the basis for a validation-testing approach
• Ø  Validation test criteria:

§  all functional requirements are satisfied,

§  all behavior characteristics are achieved,

§  all content is accurate and properly presented,

§  all performance requirements are attained, documentation is correct, and

§  usability and other requirements are met.

System testing

• A series of different tests to verify that system elements have been properly integrated and perform allocated functions.
• Type of system testing

1. Ø  Recovery Testing
2. Ø  Security Testing
3. Ø  Stress Testing
4. Ø  Performance Testing
5. Ø  Deployment Testing

Software test documentation

• IEEE 829 2008 Standard for Software Test Documentation

• The documents are

1. Ø  Test Design Specification
2. Ø  Test Case Specification
3. Ø  Test Procedure Specification
4. Ø  Test Item Transmittal Report
5. Ø  Test Log
6. Ø  Test incident Report
7. Ø  Test Summary Report

Test case design

• Focuses on a set of techniques for the creation of test cases that meet overall testing objectives and the testing strategies
• For conventional application, software is tested from two perspectives

Ø                                                      White box testing

Ø                                                       Black box testing

Drawing flow graph

 Muhammad Hazwan Bin Abu Bakar (IS085737)

Module 5

Software Implementation

Method best to study the module 

•   Use a mind map 
•  Group discussion
•  Q&A session at the end of class

Suggestion on topics that should be add or drop in the module 

•   I think in this module, it should have more example on defensive programming.

Suggestion on any other teaching and learning technique

•  At the end of the class,student should had a meeting in their small group to get more clearer about the topic.
• At the end of the lecture,student should do some Q&A with the lecturer and student. 

All the lesson learn

 Mohammad Naqib B Md Esa  (IS085723)

Module 4

Software Design

Method best to study the module

• group discussion
• do open session slot to Q&A.

Suggestion on any other teaching and learning technique to be used using lecture.

• Student should read the notes before the lecturer begin the lecture.
• Do some revision at home to create some idea how the system work.
• At the end of the class,student should had a meeting in their small group to get more clearer about the topic.
• At the end of the lecture,student should do some Q&A with the lecturer n student.

All the lesson learned.

In this chapter, there a set of design principles, concepts, and practices.

Design - creates a representation or model of the software.

             - four design models required for a complete design specification:

1. data design
2. architectural design
3. user interface design
4. component-level design

Analysis Models  Design Model

Design Concepts

 Muhammad Rijaluddin Bin Mohd Rusli (IS085739)

SE's Quiz

Quiz 1 - 4 May 2011 (chapter 1)

Quiz 2 - 22 June 2011 (chapter 2, chapter 3)

Quiz 3 - 13 July 2011 (chapter 4, chapter 5)

The question was in combination of objective and structure, quite tough for those are not do a revision. Lecturer was considered and agree with answer that we wrote even the answer are in Malay, thanks mam :)

 

Muhammad Rijaluddin Bin Mohd Rusli (IS085739)

Module 3 PART 2

Requirement Engineering

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 the lesson learned.

• There are two types of approaches for technical modeling that is STRUCTURED ANALYSIS and OBJECT-ORIENTED ANALYSIS.
• OO concepts, which include objects, classes, attributes, methods, sub-class, super-class and classification of oo modeling is scenario based,class baesd and behavioral.
• Class-based modeling - Depicts a collection of system’s classes, their attributes, and the relationships between the classes.
• Behavioral modeling - Make a list of the different states of a system and it have sequence diagram to detail how operation carried out
• Use case is a diagram that follow the actor and use cases that must draw by follow the shape.there have another relationship in use case that is uses and extends.

                                                 Muhammad Hazwan b Abu Bakar  IS085737

Module 3 PART 1

Requirement Engineering

Method best to study the module

• form a small group in a class,do some discussion with each groupmate about the sub topic.
• ask each group to create some sketch to analyze the data flow.
• do open session slot to Q&A.

Suggestion on topics that should be added or dropped from the module.

• There is no suggestion, I guess.

Suggestion on any other teaching and learning technique to be used using lecture.

• Student should read the notes before the lecturer begin the lecture.
• Do some revision at home to create some idea how the system work.
• At the end of the class,student should had a meeting in their small group to get more clearer about the topic.
• At the end of the lecture,student should do some Q&A with the lecturer n student.

All the lesson learned.

• There are two types of requirements there is FUNCTIONAL REQUIREMENTS(FR) & NON-FUNCTIONAL REQUIREMENTS.
• Functional requirement will contain a unique name and number, a brief summary, and a rationale.
• Requirements engineering(RE) applies to the development of all sof tware - intensive systems, but not necessarily to the development of all software
• There are several task of RE process that is Requirement elicitations, analysis and negotiation, software requirements specification(SRS), verification and validation, managements.
• All of this task have their own techniques, various methods, and approaches for performing and supporting the RE process.

Muhammad Hazwan Bin Abu Bakar IS085737