NYU. Business Solution Engineering Project Sample Application XXX



Similar documents
Software Engineering G

New York University Computer Science Department Courant Institute of Mathematical Sciences

Requirements Management Practice Description

Developing Business Architecture with TOGAF

A Comparison of SOA Methodologies Analysis & Design Phases

Managing the Services Lifecycle SOA & BPM

Approach to Service Management

Program Lifecycle Methodology Version 1.7

Software Engineering. Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti

<Project Name> Quality Assurance Plan

SOMA, RUP and RMC: the right combination for Service Oriented Architecture

TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION

The Role of the Software Architect

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice

Appendix 2-A. Application and System Development Requirements

Requirements Elaboration

U.S. Department of Education Federal Student Aid

Requirements Definition and Management Processes

Estimating Impact of Change

Plan-Driven Methodologies

Service-Oriented Architecture Maturity Self-Assessment Report. by Hewlett-Packard Company. Developed for Shrinivas Yawalkar Yawalkar of CTS

Chap 1. Introduction to Software Architecture

Software Development in the Large!

U.S. Department of Education Federal Student Aid

Leveraging RUP, OpenUP, and the PMBOK. Arthur English, GreenLine Systems

DATABASE DESIGN. - Developing database and information systems is performed using a development lifecycle, which consists of a series of steps.

Auditing the Software Development Lifecycle ISACA Geek Week. Mike Van Stone Sekou Kamara August 2014

Background: Business Value of Enterprise Architecture TOGAF Architectures and the Business Services Architecture

Development of Enterprise Architecture of PPDR Organisations W. Müller, F. Reinert

Classical Software Life Cycle Models

Guide to Enterprise Life Cycle Processes, Artifacts, and Reviews

Project Initiation. ProPath. Office of Information and Technology

NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0

Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK

How To Understand The Business Analysis Lifecycle

Web Service Implementation Methodology

How To Understand The Software Process

Non-Functional Requirements

Analysis of the Specifics for a Business Rules Engine Based Projects

Foundations of Model-Driven Software Engineering

Increasing Development Knowledge with EPFC


<Project Name> Configuration Management Plan

The Rap on RUP : An Introduction to the Rational Unified Process

Enterprise Security Architecture for Cyber Security. M.M.Veeraragaloo 5 th September 2013

Software Engineering. Christopher Simpkins Chris Simpkins (Georgia Tech) CS 2340 Objects and Design CS / 16

CS4507 Advanced Software Engineering

Design Specification for IEEE Std 1471 Recommended Practice for Architectural Description IEEE Architecture Working Group 0 Motivation

Chapter 4 Software Lifecycle and Performance Analysis

The most suitable system methodology for the proposed system is drawn out.

A Software process engineering course

Product Development Best Practices

The role of integrated requirements management in software delivery.

Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology

SYLLABUS CIS 3660: OBJECT-ORIENTED SYSTEM ANALYSIS AND DESIGN SPRING 2010

Software Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville

Content Management Using Rational Unified Process Part 1: Content Management Defined

Software Quality Assurance Plan

Reference Process for Enterprise Architecture enabled ICT Planning

Global Delivery Excellence Best Practices for Improving Software Process and Tools Adoption. Sunil Shah Technical Lead IBM Rational

Managing Change Using Enterprise Architecture

Frank Tsui. Orlando Karam. Barbara Bernal. State. University. Polytechnic. Ail of Southern JONES & BARTLETT LEARNING

!! " "!! # $ % " & ' $ % (! %) * +, $ ( ) ' " -

An Actual Implementation of a UML Profile for Developing Airworthiness- Compliant (RTCA DO-178B) Software.

Enterprise Test Management Standards

Module F13 The TOGAF Certification for People Program

Sparx Enterprise Architect for Business Analysts

Automotive System and Software Architecture

Service Oriented Architecture Design and Development Method. Name: René van Donselaar. Universiteit Utrecht

Software Development Life Cycle (SDLC)

Basic Unified Process: A Process for Small and Agile Projects

Data Modeling Basics

WHITE PAPER DATA GOVERNANCE ENTERPRISE MODEL MANAGEMENT

Co-Creation of Models and Metamodels for Enterprise. Architecture Projects.

Agile Business Process Modelling Framework and Enterprise Architecture.

A Software Development Platform for SOA

Content Management Using the Rational Unified Process By: Michael McIntosh

How To Understand And Understand The Software Development Process In Korea

A Capability Maturity Model (CMM)

Value to the Mission. FEA Practice Guidance. Federal Enterprise Architecture Program Management Office, OMB

Sparx Systems Enterprise Architect for Team Players

STS Federal Government Consulting Practice IV&V Offering

UML TUTORIALS THE COMPONENT MODEL

US Department of Education Federal Student Aid Integration Leadership Support Contractor January 25, 2007

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction

Concept of Operations for Line of Business Initiatives

Department of Administration Portfolio Management System 1.3 June 30, 2010

Introduction to the IBM Rational Software Development Platform

Extend the value of your core business systems.

Organization. Project Name. Project Overview Plan Version # Date

Advanced Topics for TOGAF Integrated Management Framework

Standards Initiatives for Software Product Line Engineering and Management within the International Organization for Standardization

A Variability Viewpoint for Enterprise Software Systems

How To Write An Slcm Project Plan

Standards for Developing and Implementing Administrative Systems at UC Davis

CDC UNIFIED PROCESS PRACTICES GUIDE

Transcription:

NYU Business Solution Engineering Project Sample Application XXX Great things are not done by impulse, but by a series of small things brought together. Vincent Van Gogh Authors: xxx Version Number: 1.0

Publication Record Version Number 1.0 (partial number when in Draft) Date Issued Primary Author Description Xxx xxx Initial Release 1

Table of Contents 1 Introduction... 6 2 EAMF-Augmented Solution/Software Development Lifecycle for Sample Application XXX... 6 2.1 Project Governance Standard...6 2.2 Using the EAMF Methodology as Part of an SDLC...6 2.3 Project Management Detailed...6 2.4 Wiki-Based Project Collaboration...6 3 EAMF Requirements Model Engineering... 6 3.1 Requirements Engineering for Sample Application XXX...6 3.1.1 Requirements Definition Methodology...6 3.1.1.1 Project Requirements Types and Categories...6 3.1.1.2 Requirements Relationships...6 3.1.1.3 Suggested Requirements Definition Steps...6 3.1.1.4 Tests Requirements Definition Methodology...6 3.1.1.5 Requirements and Tests Management...6 3.1.2 RequisitePro Implementation Details...6 3.2 EAMF Requirements Model Engineering for Sample Application XXX...6 3.2.1 EAMF Framework and Methodology Aspects...6 3.2.1.1 Project Requirements Model Categories...7 3.2.1.2 EAMF Requirements Model Relationships...7 3.2.1.3 Mapping Requirements into the EAMF Requirements Model...8 3.2.1.4 Reasoning about Business Entities Dependencies and Goals...8 3.2.1.5 Documenting Requirements Modeling Activities...8 3.2.1.6 Populating Requirements Model Categories...8 3.2.1.7 Building Requirements Models Iteratively...8 3.2.2 EAMF Requirements Model Engineering Implementation for Sample Application XXX...8 3.2.2.1 Sparx Systems EA Implementation Details...8 3.2.2.2 IBM Rational ReqPro Implementation Details...8 3.2.2.3 Additional EAMF Implementation Tools...8 3.2.2.4 EAMF Catalog Database...8 3.3 Requirements Engineering and EAMF Requirements Model Engineering for Sample Application XXX...8 3.3.1 Requirements Definition for Sample Application XXX...8 3.3.2 EAMF Requirements Model Engineering for Sample Application XXX...8 3.3.2.1 Mapping Requirements into the EAMF Requirements Model...8 3.3.2.2 Reasoning about Business Entities Dependencies and Goals...8 4 Business Architecture Model Development Methodology... 8 4.1 Analysis...8 4.1.1 EAMF Framework and Methodology Aspects...8 4.1.1.1 Identifying Entities and their Relationships...8 4.1.1.2 Business Use Case Modeling...8 4.1.1.3 Documenting the Conceptual Business Architecture...8 4.1.1.4 Business Process Modeling via URN Modeling...9 4.1.1.5 Organization and Location Modeling...9 4.1.1.6 Identifying Candidate Business Patterns...9 4.1.1.7 Identifying Candidate Reference Projects...9 4.1.2 EAMF Business Architecture Analysis Implementation...9 4.1.2.1 Sparx Systems EA Implementation Details...9 4.1.2.2 Additional EAMF Implementation Tools...9 2

4.2 Design...9 4.2.1 EAMF Framework and Methodology Aspects...9 4.2.1.1 URN Design Model Elicitation...9 4.2.1.2 Business Architecture Reuse Constraints Elicitation...9 4.2.1.3 Business Architecture Patterns Constraints Elicitation...9 4.2.1.4 Business Architecture Model Elicitation...9 4.2.2 EAMF Business Architecture Design Implementation...9 4.2.2.1 Sparx Systems EA Implementation Details...9 4.2.2.2 Additional EAMF Implementation Tools...9 4.3 Methodology Summary...9 4.4 Business Architecture for Sample Application XXX...9 4.4.1 Business Architecture High-Level Analysis for Sample Application XXX...9 4.4.1.1 Identifying Entities and their Relationships...9 4.4.1.2 Business Use Case Modeling...9 4.4.1.3 Documenting the Conceptual Business Architecture...10 4.4.1.4 Business Process Modeling via URN Modeling...10 4.4.1.5 Organization and Location Modeling...10 4.4.1.6 Identifying Candidate Business Patterns...10 4.4.1.7 Identifying Candidate Reference Projects...10 4.4.2 Business Architecture High-Level Design for Sample Application XXX...10 4.4.2.1 URN Design Model Elicitation...10 4.4.2.2 Business Architecture Reuse Constraints Elicitation...10 4.4.2.3 Business Architecture Patterns Constraints Elicitation...10 4.4.2.4 Business Architecture Model Elicitation...10 4.4.3 Business Architecture Detailed Analysis for Sample Application XXX...10 4.4.4 Business Architecture Detailed Design for Sample Application XXX...10 5 Information Architecture Development Methodology... 10 5.1 Analysis...10 5.2 Design...10 5.3 Methodology Summary...10 5.4 Information Architecture for Sample Application XXX...10 6 Application Architecture Development Methodology... 10 6.1 Analysis...10 6.2 Design...11 6.3 Methodology Summary...11 6.4 Application Architecture for Sample Application XXX...11 7 Technology Architecture Development Methodology... 11 7.1 Analysis...11 7.2 Design...11 7.3 Methodology Summary...11 7.4 Technology Architecture for Sample Application XXX...11 8 Enterprise Architecture Development Methodology... 11 8.1 Business Strategy Aspects...11 8.2 Governance Aspects...11 8.3 Business, Information, Application, and Technology Architecture Oversight Aspects...11 8.4 Enterprise Architecture Aspects for Sample Application XXX...11 9 EAMF-Based Solution Construction Aspects... 11 9.1 Construction Approach...11 9.1.1 Construction Methodology...11 9.1.2 Construction Methodology Implementation...12 9.2 Methodology Summary...12 3

9.3 Sample Application XXX Construction...12 10 EAMF-Based Solution Transition Aspects... 12 10.1 Transition Approach...12 10.1.1 Transition Methodology...12 10.1.2 Transition Methodology Implementation...12 10.2 Methodology Summary...12 10.3 Sample Application XXX Transition...12 11 EAMF-Based Project Collaboration Framework... 12 11.1 Collaboration Shell...12 11.2 Requirements Engineering Artifacts Visibility...12 11.3 EAMF Artifacts Visibility...12 11.4 Software Development Artifacts Visibility...12 11.5 Software Artifacts Visibility...12 11.6 Maintenance Artifacts Visibility...12 11.7 EAMF-Based Project Collaboration Framework for Sample Application XXX...12 12 Conclusion:... 13 Glossary... 14 References... 15 Appendix A: IBM Rational ReqPro Partial Report for Sample Application XXX... 16 Appendix B: Business Architecture Artifacts Catalog for Sample Application XXX... 16 Appendix C: Information Architecture Artifacts Catalog for Sample Application XXX... 16 Appendix D: Application Architecture Artifacts Catalog for Sample Application XXX... 16 Appendix E: Technology Architecture Artifacts Catalog for Sample Application XXX... 16 Appendix F: Enterprise Architecture Artifacts Catalog for Sample Application XXX... 16 Appendix G: Construction Artifacts Catalog for Sample Application XXX... 16 Appendix H: Transition Artifacts Catalog for Sample Application XXX... 16 Appendix I: Collaboration Framework Artifacts Catalog for Sample Application XXX... 16 Appendix J: EAMF Framework Summarized... 16 Appendix K: EAMF UML 2.0 Metamodel... 16 4

Table of Figures 5

1 Introduction 2 EAMF-Augmented Solution/Software Development Lifecycle for Sample Application XXX 2.1 Project Governance Standard 2.2 Using the EAMF Methodology as Part of an SDLC 2.3 Project Management Detailed 2.4 Wiki-Based Project Collaboration 3 EAMF Requirements Model Engineering 3.1 Requirements Engineering for Sample Application XXX 3.1.1 Requirements Definition Methodology 3.1.1.1 Project Requirements Types and Categories 3.1.1.2 Requirements Relationships 3.1.1.3 Suggested Requirements Definition Steps 3.1.1.4 Tests Requirements Definition Methodology 3.1.1.5 Requirements and Tests Management 3.1.2 RequisitePro Implementation Details 3.2 EAMF Requirements Model Engineering for Sample Application XXX 3.2.1 EAMF Framework and Methodology Aspects 6

3.2.1.1 Project Requirements Model Categories 3.2.1.2 EAMF Requirements Model Relationships 7

3.2.1.3 Mapping Requirements into the EAMF Requirements Model 3.2.1.4 Reasoning about Business Entities Dependencies and Goals 3.2.1.5 Documenting Requirements Modeling Activities 3.2.1.6 Populating Requirements Model Categories 3.2.1.7 Building Requirements Models Iteratively 3.2.2 EAMF Requirements Model Engineering Implementation for Sample Application XXX 3.2.2.1 Sparx Systems EA Implementation Details 3.2.2.2 IBM Rational ReqPro Implementation Details 3.2.2.3 Additional EAMF Implementation Tools 3.2.2.4 EAMF Catalog Database 3.3 Requirements Engineering and EAMF Requirements Model Engineering for Sample Application XXX 3.3.1 Requirements Definition for Sample Application XXX 3.3.2 EAMF Requirements Model Engineering for Sample Application XXX 3.3.2.1 Mapping Requirements into the EAMF Requirements Model 3.3.2.2 Reasoning about Business Entities Dependencies and Goals 4 Business Architecture Model Development Methodology 4.1 Analysis 4.1.1 EAMF Framework and Methodology Aspects 4.1.1.1 Identifying Entities and their Relationships 4.1.1.2 Business Use Case Modeling 4.1.1.3 Documenting the Conceptual Business Architecture 8

4.1.1.4 Business Process Modeling via URN Modeling 4.1.1.5 Organization and Location Modeling 4.1.1.6 Identifying Candidate Business Patterns 4.1.1.7 Identifying Candidate Reference Projects 4.1.2 EAMF Business Architecture Analysis Implementation 4.1.2.1 Sparx Systems EA Implementation Details 4.1.2.2 Additional EAMF Implementation Tools 4.2 Design 4.2.1 EAMF Framework and Methodology Aspects 4.2.1.1 URN Design Model Elicitation 4.2.1.2 Business Architecture Reuse Constraints Elicitation 4.2.1.3 Business Architecture Patterns Constraints Elicitation 4.2.1.4 Business Architecture Model Elicitation 4.2.2 EAMF Business Architecture Design Implementation 4.2.2.1 Sparx Systems EA Implementation Details 4.2.2.2 Additional EAMF Implementation Tools 4.3 Methodology Summary 4.4 Business Architecture for Sample Application XXX 4.4.1 Business Architecture High-Level Analysis for Sample Application XXX 4.4.1.1 Identifying Entities and their Relationships 4.4.1.2 Business Use Case Modeling 9

4.4.1.3 Documenting the Conceptual Business Architecture 4.4.1.4 Business Process Modeling via URN Modeling 4.4.1.5 Organization and Location Modeling 4.4.1.6 Identifying Candidate Business Patterns 4.4.1.7 Identifying Candidate Reference Projects 4.4.2 Business Architecture High-Level Design for Sample Application XXX 4.4.2.1 URN Design Model Elicitation 4.4.2.2 Business Architecture Reuse Constraints Elicitation 4.4.2.3 Business Architecture Patterns Constraints Elicitation 4.4.2.4 Business Architecture Model Elicitation 4.4.3 Business Architecture Detailed Analysis for Sample Application XXX 4.4.4 Business Architecture Detailed Design for Sample Application XXX 5 Information Architecture Development Methodology 5.1 Analysis 5.2 Design 5.3 Methodology Summary 5.4 Information Architecture for Sample Application XXX 6 Application Architecture Development Methodology 6.1 Analysis 10

6.2 Design 6.3 Methodology Summary 6.4 Application Architecture for Sample Application XXX 7 Technology Architecture Development Methodology 7.1 Analysis 7.2 Design 7.3 Methodology Summary 7.4 Technology Architecture for Sample Application XXX 8 Enterprise Architecture Development Methodology 8.1 Business Strategy Aspects 8.2 Governance Aspects 8.3 Business, Information, Application, and Technology Architecture Oversight Aspects 8.4 Enterprise Architecture Aspects for Sample Application XXX 9 EAMF-Based Solution Construction Aspects 9.1 Construction Approach 9.1.1 Construction Methodology 11

9.1.2 Construction Methodology Implementation 9.2 Methodology Summary 9.3 Sample Application XXX Construction 10 EAMF-Based Solution Transition Aspects 10.1 Transition Approach 10.1.1 Transition Methodology 10.1.2 Transition Methodology Implementation 10.2 Methodology Summary 10.3 Sample Application XXX Transition 11 EAMF-Based Project Collaboration Framework 11.1 Collaboration Shell 11.2 Requirements Engineering Artifacts Visibility 11.3 EAMF Artifacts Visibility 11.4 Software Development Artifacts Visibility 11.5 Software Artifacts Visibility 11.6 Maintenance Artifacts Visibility 11.7 EAMF-Based Project Collaboration Framework for Sample Application XXX 12

12 Conclusion: 13

Glossary Term Definition 14

References Information Source 15

Appendix A: IBM Rational ReqPro Partial Report for Sample Application XXX Appendix B: Business Architecture Artifacts Catalog for Sample Application XXX Appendix C: Information Architecture Artifacts Catalog for Sample Application XXX Appendix D: Application Architecture Artifacts Catalog for Sample Application XXX Appendix E: Technology Architecture Artifacts Catalog for Sample Application XXX Appendix F: Enterprise Architecture Artifacts Catalog for Sample Application XXX Appendix G: Construction Artifacts Catalog for Sample Application XXX Appendix H: Transition Artifacts Catalog for Sample Application XXX Appendix I: Collaboration Framework Artifacts Catalog for Sample Application XXX Appendix J: EAMF Framework Summarized Appendix K: EAMF UML 2.0 Metamodel 16