4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM 2012391167 SYARIFAH SYAZA BTE SEYD ZULKAFLY 2012193761 CS230(5A)

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

National Association for Regulatory Administration September 13, 2011 IT’s NOT Like Building a House Mark Parker (800)
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Lecture # 2 : Process Models
Software Development Life Cycle
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
CS487 Software Engineering Omar Aldawud
Chapter 2 Approaches to System Development
CHAPTER TWO Object Oriented System Analysis and Design 1.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
Chapter 2 – Software Processes
Ch 3 System Development Environment
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Software Process and Problem Statements CSSE 371, Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 3, 2004.
Systems Analysis and Design in a Changing World, Fifth Edition
COMP 350: Object Oriented Analysis and Design Lecture 2
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
CHAPTER 17 Building Software to Support an Agile Organization
Chapter 1 The Systems Development Environment
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
CIS 321—IS Analysis & Design
Chapter 2: Approaches to System Development
RAD Model BY - Dhivakaran.JM.
Chapter 2 The process Process, Methods, and Tools
Transforming Organizations
Business Driven Technology Unit 5 Transforming Organizations McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved.
THE PROTOTYPING MODEL The prototyping model begins with requirements gathering. Developer and customer meet and define the overall objectives for the software.
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
Presentation Handout EDBA – Module 8 Information Technology 30 th November 2014 By K.M.Prashanthan.
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
2 Systems Analysis and Design in a Changing World, Fifth Edition.
Systems Analysis and Design in a Changing World, Fourth Edition
Project – A Quick Tutorial Krishna Sainath Meda. PROJECT  A task assigned to a set of people or teams to be completed within a time frame  Any project.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Software Project Management Iterative Model & Spiral Model.
Agile febrian | erlien | beny | ragnar | billy. SLDC Methodologies.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Systems Development Life Cycle
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.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Systems Development Process and Methodologies Dr. T. Ravichandran.
Chapter 2: The Process. What is Process? Software Engineering Process is the glue that holds the technology layers together and enables rational and timely.
Software Engineering cosc 4359 Spring 2017.
TK2023 Object-Oriented Software Engineering
Methodologies and Algorithms
Software development life cycle models
Software Process Models
Software Process Models
Software Life Cycle Models
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Introduction to Software Engineering
COMP 350: Object Oriented Analysis and Design Lecture 2
Lecture 2 Revision of Models of a Software Process
Software Development Process
Software Process Models
Incremental Waterfall
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Software Engineering Lecture 17.
Project Lifecycle and IT Product Life Cycle
Lecture 4 Project Management in ICT
Presentation transcript:

4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)

A framework that is used to structure, plan, and control the process of developing an information system.

Waterfall Object oriented Rapid application development (RAD ) Model view controller (MVC) Prototyping Spiral Rapid application development(R AD) Extreme Agile

A linear-sequential life cycle model. In a waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phase. The sequential phases in Waterfall model are:  Requirement Gathering and analysis  System Design  Implementation  Integration and Testing  Deployment of system  Maintenance

The spiral model has four phases. A software project repeatedly passes through these phases in iterations called Spirals.  Identification: This phase starts with gathering the business requirements in the baseline spiral. In the subsequent spirals as the product matures, identification of system requirements, subsystem requirements and unit requirements are all done in this phase.  Design: Design phase starts with the conceptual design in the baseline spiral and involves architectural design, logical design of modules, physical product design and final design in the subsequent spirals.  Construct or Build: Construct phase refers to production of the actual software product at every spiral. In the baseline spiral when the product is just thought of and the design is being developed a POC (Proof of Concept) is developed in this phase to get customer feedback.  Evaluation and Risk Analysis: Risk Analysis includes identifying, estimating, and monitoring technical feasibility and management risks, such as schedule slippage and cost overrun. After testing the build, at the end of first iteration, the customer evaluates the software and provides feedback.

Following are the Agile Manifesto principles:  Individuals and interactions - in agile development, self-organization and motivation are important  Working software - Demo working software is considered the best means of communication with the customer to understand their requirement, instead of just depending on documentation.  Customer collaboration - As the requirements cannot be gathered completely in the beginning of the project due to various factors, continuous customer interaction is very important to get proper product requirements.  Responding to change - agile development is focused on quick responses to change and continuous development.

RAD model distributes the analysis, design, build, and test phases into a series of short, iterative development cycles. Following are the phases of RAD Model:  Business Modeling: The business model for the product under development is designed in terms of flow of information and the distribution of information between various business channels  Data Modeling: The information gathered in the Business Modeling phase is reviewed and analyzed to form sets of data objects vital for the business. The attributes of all data sets is identified and defined. The relation between these data objects are established and defined in detail in relevance to the business model.  Process Modeling: The data object sets defined in the Data Modeling phase are converted to establish the business information flow needed to achieve specific business objectives as per the business model. The process model for any changes or enhancements to the data object sets is defined in this phase. Process descriptions for adding, deleting, retrieving or modifying a data object are given.  Application Generation: The actual system is built and coding is done by using automation tools to convert process and data models into actual prototypes.  Testing and Turnover: The overall testing time is reduced in RAD model as the prototypes are independently tested during every iteration. However the data flow and the interfaces between all the components need to be thoroughly tested with complete test coverage.

FRAMEWORK Unified process Rational unified process(RUP) Microsoft solutionFramework

 The Unified Process (UP) Model is an iterative and incremental software development process framework and one of the heavyweight software development methodologies.

It divides the development process into four distinct phases that each involve business modelling, analysis and design, implementation, testing, and deployment.