SOFTWARE ENGINEERING ASSIGNMENT

Software Engineering Assignment



Software Engineering Assignment

Introduction

Application Owners will use this Procedure to create the Software Development Lifecycle (SDLC) artifacts for major application projects, as required by the SDLC Policy. This SDLC Procedure is instituted in order to support the SDLC Policy. The SDLC Policy mentions artifacts to be created through the life of a major application project. This Procedure specifies the contents of such artifacts. However, beyond the contents, this Procedure does not take a position on the appearance and formatting of such artifacts.

Applicability

The applicability of this Procedure is identical to that of the SDLC Policy.

 

Responsibilities

A. Application Owners: The Application Owners are responsible for creating the SDLC artifacts according to this Procedure and submitting them to the Enterprise Project Management Office (PMO).

B. Associate CIO, Applications: The Associate CIO, Applications, is responsible for enforcing this Procedure.

Guidelines & Procedures

A. Compliance with the SDLC Policy is measured by the successful creation of the SDLC artifacts according to this SDLC Procedure.

B. It is not the intent of the SDLC Policy and Procedure to create duplicate work. Should the Application Owners generate the contents of the SDLC artifacts under different names or contexts, then that adequately suffices in terms of compliance with the SDLC Policy.

C. The artifacts, corresponding to each SDLC Discipline, are enumerated below. The artifacts are elaborated in the Definitions section, in alphabetical order.

 Discipline

Artifacts

Business Modeling

·        Current Process Flow Diagrams

·        Legacy User Manual (Only if available, not mandatory.)

·        Legacy Operations Manual (Only if available, not mandatory.)

Requirements

·        Problem Statement

·        Desired Process Flow Diagrams

·        Desired Use Cases

Analysis & Design

·        Roles & Privileges Document

·        User Interface Prototype Document

·        Logical Database Design Document

·        Physical Database Design Document

·        Object-Relational Model Document (Only if the Business Logic is encoded in an object-oriented programming language.)

Implementation

·        New User Manual

Test

See the Deployment Certification Policy for Major Application Projects.

Deployment

·        Infrastructure Planning Document

·        New Operations Manual

 

D. The artifacts enumerated above constitute the minimum requirements in terms of compliance with the SDLC Policy. It is left to the discretion of the Application Owners to create additional SDLC documentation in support of their specific application projects.

E. Submission of the SDLC artifacts enumerated above does not preclude the necessity of submitting other project management documentation to the Enterprise PMO, concerning the overall management of the application project. The Enterprise PMO determines the scope and nature of the required project management documentation.

F. Alternative SDLC methodologies are known to use broad-based umbrella titles, such as Design Specifications, Requirements Document, etc. Contents of such titles may overlap with multiple artifacts enumerated above under Requirements and Analysis & Design. What actually matters in terms of compliance with the SDLC Policy is the content, not the title. Should it be more convenient to the Application Owners to generate the contents of the artifacts under Requirements and Analysis & Design under broad-based umbrella titles, then that adequately suffices in terms of compliance with the SDLC Policy and no duplication of effort is warranted. However, it still remains the burden of the Application Owners to prove that they have indeed generated ...