Software Engineering Lecture # 1.

Slides:



Advertisements
Similar presentations
Software Life Cycle and Models
Advertisements

S Y S T E M S E N G I N E E R I N G.
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
10 Software Engineering Foundations of Computer Science ã Cengage Learning.
The System Development Life Cycle
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Software Engineering.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Unit 191 Introduction to Software Engineering The objective of this section is to introduce the subject of software engineering. When you have read this.
Fundamentals of Information Systems, Second Edition
Systems Development Life Cycle
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
7.2 System Development Life Cycle (SDLC)
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
Software Life Cycle Model
S/W Project Management
Chapter 10.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Systems Analysis and Design
1 CMPT 275 Software Engineering Software life cycle.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Chapter 2 The process Process, Methods, and Tools
Managing the development and purchase of information systems (Part 1)
S oftware Q uality A ssurance Part One Reviews and Inspections.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Chapter 14 Information System Development
Software Life-Cycle Models Somnuk Keretho, Assistant Professor Department of Computer Engineering Faculty of Engineering, Kasetsart University
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Slide 2.1 CHAPTER 2 THE SOFTWARE PROCESS. Slide 2.2 Overview l Client, Developer, and User l Requirements Phase l Specification Phase l Design Phase l.
Software Development Life Cycle (SDLC) Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Software Engineering. Lesson 2 Explain what is a software life cycle model. Identify the different software life cycle models. – Classical Waterfall Model.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Program Development Cycle
Software Development Life Cycle (SDLC)
Software Project Management Iterative Model & Spiral Model.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Software Engineering INTRODUCTION TO SOFTWARE DEVELOPMENT.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Software Development Life cycle (SDLC). Phases of SDLC 2 Requirement Analysis (Defining Requirement) Designing (Design) Coding (Implementation) Software.
Statement of Work Lecture. SOW The statement of work is the basis of the contract between the pro- poser and the customer, and is often incorporated into.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
 System Requirement Specification and System Planning.
The System Development Life Cycle
Systems Development Life Cycle
Information Systems Development
Methodologies and Algorithms
Topic for Presentaion-2
Systems Analysis and Design
Quality Management Perfectqaservices.
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Software Development Life Cycle
Information Systems Development
The System Development Life Cycle
Engineering Processes
Software life cycle models
Software Engineering Lecture 17.
Software Development Life Cycle Models
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
SDLC (Software Development Life Cycle)
System Analysis and Design:
Presentation transcript:

Software Engineering Lecture # 1

Construction The construction activities are those that directly related to the development of software Requirement Gathering Design Development Coding Testing

Management Management activities are kind of umbrella activities that are used to smoothly and successfully perform the construction activities. Some of the major management activities are listed below: Project Planning and Management Configuration Management Software Quality Assurance Installation and Training

Development Activities

Software Development Loop Software development activities could be performed in a cyclic and that cycle is called software development loop. The major stages of software development loop are described below. Problem Definition Technical Development Solution Integration Status Quo Hardware

Continued..

Phases of software development

Software Process Software Process defines the way to produce software. I t includes Software life-cycle model Tools to use Individuals building software Software life-cycle model defines how different phases of the life cycle are managed.

Planning and Requirement Analysis Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational, and technical areas.

Continued Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.

Continued Concept exploration Determine what the client needs, not what the client wants

Defining Requirements Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through .SRS. . Software Requirement Specification document which consists of all the product requirements to be designed and developed during the project life cycle. From the customer requirements identify what to build.

Designing the product architecture From the specification identify how to build. SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.

continued The inputs from users and information gathered in requirement gathering phase are the inputs of this step. The output of this step comes in the form of two designs; logical design and physical design. Engineers produce data dictionaries, logical diagrams, data-flow diagrams.

Continued Design involves two steps Architectural Design – Identify modules Detailed Design – Design each modules Document – Architecture Document, Design Document

Continued This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, budget and time constraints , the best design approach is selected for the product.

Building or Developing the Product In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.

continued Developers have to follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers etc are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java, and PHP are used for coding. The programming language is chosen with respect to the type of software being developed

Testing the Product This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However this stage refers to the testing only stage of the product where products defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.

Deployment in the Market and Maintenance Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometime product deployment happens in stages as per the organizations business strategy. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing). Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.

Software Engineering-Definitions

Build and fix Model In this model the product is constructed without specification or any attempt at design. The developers simply build a product that is reworked as many times as necessary to satisfy the client. This model may work for small projects but is totally unsatisfactory for products of any reasonable size. The cost of build-and fix is actually far greater than the cost of properly specified and carefully designed product.

Continued.. This model includes the following two phases. Build: In this phase, the software code is developed and passed on to the next phase. Fix: In this phase, the code developed in the build phase is made error free. Also, in addition to the corrections to the code, the code is modified according to the user's requirements.

Advantages and Disadvantages

Build and fix model

Retirement Good software is maintained Sometimes software is rewritten from scratch Software is now un-maintainable because A drastic change in design has occurred The product must be implemented on a totally new hardware/operating system Documentation is missing or inaccurate Hardware is to be changed—it may be cheaper to rewrite the software from scratch than to modify it True retirement is a rare event