BCIS 4610 Project - Interim Report 1 BCIS 4610 INTERIM REPORT By : Name 1, Name 2 and Name 3. LLC

BCIS 4610 Project - Interim Report 1

BCIS 4610 INTERIM REPORT

By : Name 1, Name 2 and Name 3. LLC

PROPO

SAL CON

TENT

Executive Summary p.11

Our Understanding of your needs

And so on…

2BCIS 4610 Project - Interim Report

OVERVIEW


EXECUTIVE SU

MM

ARYExecutive Summary

This template is intended to provide guidance with regard to the expected content and presentation of the Interim Report.

Specifically, the template provides guidance on:•The sections that should be present in the report;•The approximate length of each section;•Formatting expectations – a professionally looking proposal is similar to a brochure; •Expectations regarding graphics and diagrams – you are expected to substitute the diagrams in the template with the ones related to your project.

You are encouraged to customize your template in the following ways:•Customizing the title page;•Replacing the logo;•Changing page layouts;•Changing section and sub-section titles;•Changing color schemes and replacing/adding graphics;•Changing the approach and the number of stages;•Other, given that the overall quality is not compromised.

Your executive summary should summarize the content of this specific report, including an overview of the process, data structure, design decisions, ect.


DISCU

SSION

OF TH

E CURREN

T SITUATIO

NClient or functional area description

Can come directly from the proposal. May be abridged.

Description of the as-is (old) system

Briefly describe how the system (the process you are trying to automate currently works. If you are designing a generic system, describe a typical process (make sure you change the section tytle appropriately.

Finish with problems with the old system (from your proposal)


GO

ALS OF TH

E PROJECT

The goal of the project

Use a lot of positive and flashy words. Can come directly from your proposal, unless you modified the goal.

Benefits for the client Figure 1: Goals of the project


PROJECT SCO

PEScope of the projectBe very specific to state what is within the scope of this project. You have likely changed (narrowed) your scope after your proposal. Make sure that you reflect those changes in the scope description. Make sure that your scope description is consistent with the scope reflected in your DFD.

Key deliverables

Limitations

State what is NOT in the scope of this project, but be positive


SYSTEM REQUIREMENTS


APPROACH

TO CO

LLECTING

USER REQ

UIREM

ENTS

The overall approach you followed in collecting your user requirements

Describe where you got your system requirements from. Be truthful. If you had worked for a similar place in the past and you remembered it, state it. If you used a book, mention it.

Key stakeholders of the system

Describe the key stakeholders of the system. Theoretically, these would be the people that you would collect the requirements from. Because this is a class project, you probably did not, but list the stakeholders anyway.

Sources of information

Be truthful. If you had worked for a similar place in the past and you remembered it, state it. If you used a book, mention it.


FUN

CTION

AL DESCRIPTIO

N O

F THE N

EW SYSTEM

Goal of the system, high level description

Describe what your system does briefly but clearly (should be related to the scope of the project)

Description of system functionality

This should include bullet points shortly describing each of your high level processes. Essentially this is a verbal description of your Level 0 DFD, so make a reference to your appendix here)

Relationship to other systems

Here you will describe what other systems your system will interact with.


FUN

CTION

AL DESCRIPTIO

N O

F THE N

EW SYSTEM


Use Case Name: ID: 1 Importance Level: High

Primary Actor:Short description:

Trigger: Type:

Major Inputs Source Major Outputs Destination

Major Steps Performed Information for Steps

FUN

CTION

AL DESCRIPTIO

N O

F THE N

EW SYSTEM




Trigger: Type:



FUN

CTION

AL DESCRIPTIO

N O

F THE N

EW SYSTEM




Trigger: Type:



FUN

CTION

AL DESCRIPTIO

N O

F THE N

EW SYSTEM




Trigger: Type:



FUN

CTION

AL DESCRIPTIO

N O

F THE N

EW SYSTEM




Trigger: Type:



DATA REQ

UIREM

ENTS (CO

NTIN

UE O

N TH

E NEXT PAG

E IF NECESSARY)

Brief description of the key types of data the is being created , stored and manipulated by the system

Describe your date in general . Mention all the entities, but do not describe them. DO not mention attributes and relationships. Discuss what data is manipulated within each of your processes. Make reference to the ERD and CRUD matrix in your appendix.

Entities

Define each of the entity and list its attributes. Make references to the Entity Model Reference Report.

Relationships

List all the relationships and discuss what they mean. Make references to the Entity Model Reference Report.


NO

N-FU

NCTIO

NAL REQ

UIREM

ENTS

Key considerations/archtecture

Discuss the type of the environment in which the system will be used and what considerations (speed, security, interface, etc.) are important. Discuss if the system is local or distributed, whether it should be accessed locally or via Internet, etc.

User interface requirements

Usability, aesthetics, corporate colors, web interface, mobile devices interface, etc.

Performance

Speed, transaction volume,

Security

Other (see your Dennis et al book)


DEFIN

ITION

OF W

ORK FO

R PHASE 2

Phase description

Overall description of what you need to accomplish to create your final report. Discuss whether you are going to build a prototype for the entire system represented in your DFD or just a part of it.

Key activities

This is based on your proposal and the requirements for your project

Key deliverables

This is based on the requirements for your project


DEFIN

ITION

OF W

ORK FO

R PHASE 2

Interface Design - Forms

List and briefly describe all forms that you will need to design for your final report. You should generally have one or one report for each of the Level 1 process.

Interface Design – Reports

List all reports that you will need to design for your final report. You should generally have one or one report for each of the Level 1 process.

Key queries

Identify what ad-hoc queries will need to be answered with your system


PHASE 2 TIM

ELINE

Schedule update and phase 2 timeline

Describe how you are doing with regard with your original time line. Mention any adjustments.

Project plan

Paste your Gantt chart with a detailed phase 2 schedule.


APPENDIX


APPEND

IXGuide to the appendix

List all elements of your appendix, preferably numbered or otherwise identified, including:• Level 0 and Level 1 DFDs• Business Process Maps• ERD• Crud Matrix• Functional Hierarchy Diagram• Entity Model Reference Report• Function Definition Report• Dataflow and data store definition reports



Documents

BCIS 4610 Project - Interim Report 1 BCIS 4610 INTERIM REPORT By : Name 1, Name 2 and Name 3. LLC