• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content


Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Team pi






Total Views
Views on SlideShare
Embed Views



1 Embed 97

http://community.mis.temple.edu 97



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Team pi Team pi Presentation Transcript

    • Team PI: Joey Klein Thomas Preston Sulay Desai Application Development Methodologies Project
    • Chosen Methodologies:
      • Rational Unified Process
      • Integrated Definition (IDEF)
      • Information Engineering
    • Rational Unified Process
      • What is Rational Unified Process?
        • RUP is an iterative software development process framework.
        • It was created by the Rational Software Corporation, which was later acquired by IBM in 2003.
    • RUP’s Life Cycle Phases
      • Inception Phase: In this phase the business case is stated. It is very important to primarily scope out the project and define what will be needed.
      • Elaboration: In this phase developers analyze the project and architecture foundation. This phase is important because during this time the developers also evaluate the risks associated with the scope of the project to make sure all risks will return rewards.
    • Rational Unified Process Contd.
      • Construction Phase: In this phase the development of the project is completed. Project is then tested to determine if deliverables are met.
      • Transition Phase: In this phase any final tuning is done. The transition phase moves the project from the development stage into the production stage, and prepares it for the end user.
    • RUP Pros and Cons
      • Pros
      • It has a popular language (UML)
      • Strong tool support
      • Takes advantage of saved templates, and progressive integration
      • Cons
      • Customizable confusion
      • RUP is not for all scale projects
    • Integrated Definition (IDEF)
      • Refers to a family of modeling languages in the field of systems and software engineering.
      • Developed by the United States Air Force.
      • Designed to cover a wide range of uses, from funtional modeling to data, simulation, object oriented analysis/design and knowledge acquisition.
    • History
      • IDEF originally stood for ICAM definition language.
      • ICAM stands for Integrated Computer-Aided Manufacturing .
      • IDEF grew out of manufacturing to become a system for companywide modeling.
        • Currently applicable to many processes other than manufacturing.
    • Application
      • There are 15 different levels of IDEF.
        • Each level serves to model a process distinctly from the rest.
      • The most commonly used IDEF models are:
        • IDEF0: Function Modeling
        • IDEF1: Information Modeling
        • IDEF1x: Data Modeling
        • IDEF2: Simulation Model Design
        • IDEF14: Network Design
    • IDEF Pros and Cons
      • Pros
      • Historically proven methodology.
      • Detailed format leaves little room for error.
      • Diverse applications means that almost all design/planning issues can be solved using IDEF.
      • Standardized for large scale adaptability
      • Cons
      • Old (lacks the ability to interact with modern technology).
      • Limited symbol set.
      • Complex and confusing to novice users.
    • Information Engineering
      • Was created in the 1980’s by Clive Finkelstein
      • Is a methodology that is geared towards computer system applications.
      • Unlike most methods doesn’t deal with business strategies.
      • Was originally used mostly by database administrators.
      • Presently used for various technical system designs.
    • Information Engineering Contd.
      • IEM uses a similar design that is comparable to the Waterfall method.
      • Rapid Application Development procedures can also be applied to IEM. Modeling and code generating tools can also be used to speed up the development process.
      • Currently many new programs/tools such as SAP are making the process of Information Engineering a lot simpler or even irrelevant.
    • IEM Life Cycles
      • Information system strategy study - analysis of the business strategy that was put forth earlier from stakeholders.
      • Feasibility study - decide if the company should build a new system or use existing programs/tools
      • Logical and Physical design – Create an ERD, data flow diagram, or other applicable deliverable that outlines the system’s skeletal design
      • Development/Construction – Writing the code for the system
      • Transition/Implementation – phasing in the new system to replace the legacy system.
    • IEM Pros and Cons
      • Structurally sound because of waterfall style.
      • Deliverables can be inputs for following phases
      • Easy to follow, even for the inexperienced practitioner
      • Time Consuming
      • Lacks Quality Assurance Checkpoints
      • Dead-end Deliverables
      • Pros
      • Cons