Software Engineering ppt...3

Views:
 
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

Software engineering:

Software engineering Dhanashree&Bhagyashree

Contents:

Contents System Development Life Cycle(SDLC). Software Testing Fundamentals ,Terminology. Software Quality fundamentals. Software Project Management.

Introduction:

Introduction Developmentof procedures and systematic applications that are used on electronic machines Software engineering incorporates various accepted methodologies to design software .

System Development Life Cycle:

System Development Life Cycle SDLC refers to a methodology for developing systems.  It provides a consistent framework of tasks and deliverables needed to develop systems.

Stages of SDLC:

Stages of SDLC Maintanance Identification Feasibility Analysis Testing Implimentation Design

Software Testing:

Software Testing Software testing is a process used to identify Correctness Completeness Quality of develop software

Software Testing Fundamentals:

Software Testing Fundamentals White Box Testing. Black Box Testing. Integration Testing. Regression Testing. System Testing.

White Box Testing:

White Box Testing Code Testing. Static Testing. Code Style Testing .

Black Box Testing:

Black Box Testing Functional Testing Performance Testing Stress Testing Security Testing Documentation Testing

Integration Testing:

Integration Testing Integration testing is used to check out the interface of the software Types Non Incremental Incremental

No incremental Testing:

No incremental Testing Unit -A Unit-B Unit -C Unit -D System Test

Incremental Testing:

Incremental Testing Module1 Module2 Module3 Module4 Module5 Module6 Module7 Module8

Regression Testing:

Regression Testing Correct error promtly . Perform on function not on design. Make changes to the data and find out its effect. Perform the repeatative task.

System Testing:

System Testing Recovery Testing Security Testing Performance Testing

Software Quality:

Software Quality

Software Quality Software quality measures how well software is designed and how well the software conforms to that design although there are several different definition. “A product quality is a function of how much it changes the world for the better.” :

Software Quality S oftware quality measures how well software is designed and how well the software conforms to that design although there are several different definition. “A product quality is a function of how much it changes the world for the better.”

Software Quality Factors 1. Understandability: The purpose of software product is clear 2.Completeness: All parts of software product are present and each parts is fully developed. 3. Conciseness: No excessive information is present. 4.Portability: The software product can be easily operated or made to operate on computer configuration. 5.Consistency: The software contains uniform notation. :

Software Quality Factors 1 . Understandability : The purpose of software product is clear 2. Completeness : All parts of software product are present and each parts is fully developed. 3. Concisenes s: No excessive information is present. 4. Portability : The software product can be easily operated or made to operate on computer configuration. 5. Consistency : The software contains uniform notation. Software Quality Factors 1 . Understandability : The purpose of software product is clear 2. Completeness : All parts of software product are present and each parts is fully developed. 3. Concisenes s: No excessive information is present. 4. Portability : The software product can be easily operated or made to operate on computer configuration. 5. Consistency : The software contains uniform notation.

Slide 18:

6.Maintainability: The product facilitates updating to satisfy new requirement. 7. Testability :The software product facilitates the establishment of acceptance criteria and support evaluation of its performance. 8. Usabilit y:the product is convenient and practicable to use. 9. Reliability :The software can be expected to perform its intended functions satisfactorily over a period of time.

Software project management:

Software project management

Software project management:

Software project management Software project management involves the planning, monitoring, & control of the people, process, & events that occurs as software evolves from a preliminary concept to an operational implementation. Effective software project management focuses on the four P’s People, Product, Process, project .

Slide 21:

The people The people factor is so important that the software engineering has developed a people management capability maturity models (PM-CMM) to enhance the the readiness of software org. to undertake increasingly complex application by helping to attract, grow, motivate, deploy, & retain the talent needed to improve their software development capability. Software process included: 1. Senior Managers 2. Project Manager 3.Practitioners 4. Customers 5. End user The Product The final deliverable of a software project is a product, which is also called as software solution.

Slide 22:

The Process The software process can be defined as a collection of pattern that defined a set of activities. A software process provide the framework form which a comprehensive plan for software development can be established. The Project A project is like a road trip. Some project are simple and routine, like driving to the store in broad daylight. But most project worth doing are more like driving a truck off road line in the mountains at night. We conduct planned and controlled software project for one primary reason it is the only know way to manage complexity.

PROJECT ESTIMATION:

PROJECT ESTIMATION Introduction Decomposition techniques Software sizing Problem based estimation LOC based estimation FP based estimation

Slide 24:

Project estimation Introduction Would you build a house without knowing how much you were about to spend, the task you needed to perform, & the time line for the work to be conducted? Of course not, & since most computer based system & product cost considerably more to build than a large house, it would seem reasonable to develop an estimation before you start creating the software. Software project are typically controlled by four major variable; Time, Requirements, Resources and Risk. Estimation begins with a description of the scope of the product. The problem is then decompose into a set of smaller problems, & each of these is estimated using historical data and experience as guides. Problem complexity and risk are considered before a final product. Decomposition Technique Decomposition can be useful tool when managing projects. Decomposition is a technique used in project management that break down the work load and task before the creation of the work breakdown structure. This important step can save time in the long run

Slide 25:

Software sizing Software sizing is an important activity in software engineering that is used to estimate the size of a software application or component in order to be able to implement other software project management activities. LOC based estimation Line of code is a measure of the size of the system after it is built. It is very dependent on the technology used to build the system, the system design and how the program are coded. The major disadvantage of LOC that are that system coded in different language cannot be easily compared and efficient code is penalized by having a smaller size. LOC of code method measure software and the process by which it is being developed. FP based estimation A function point is a measurement to express the amount of business functionality information system provided to user. The cost of single unit is calculated form past projects. Function points are the units measure used by the IFPUG function size measurement method.

PROJECT SCHEDULING:

PROJECT SCHEDULING Basic concept Project scheduling Basic principles The relationship between People & Efforts Effort distribution Defining a task network CPM/PERT

Slide 27:

Project scheduling Essentially, driving without any idea of how you’re going to get there is the same as working on a project without schedule. No matter the size or scope of your project the schedule is a part of project management. The schedule tell you when each activity should done, what was already been completed. And the sequence in which things need to be finished. Scheduling is an inexact process in that is tries to predict the future. Basic principles Compartmentalization- The project must be compartmentalization in to a number of manageable activity and task. Interdependency- The interdependency of each compartmentalized activity, action, or task must be determined.

Slide 28:

Time allocation- Each task to be schedule must be allocated some number of units . Effort Validation- Every project has a defied number of people on the software team. As time allocation occurs the project manager must ensure that no more than the allocated number of people has been Schedule at any given time. Defined Responsibility- Defined outcomes- Defined Milestone-

Slide 29:

Effort distribution- Effort distribution should be used as a guideline only. The characteristics of each project must dictate the distribution of efforts. The effort applied to software design. Task network- A task network also called an activity network is a graphically representation of the task flow for a project. CPM/PERT- Critical path method and the program evaluation and review technique.

THANK YOU:

THANK YOU

authorStream Live Help