guidance to interim report 31052011

8/6/2019 Guidance to Interim Report 31052011

1/35

Guidance to Interim Report

Being more Efficient


2/35

Interim Report

Progress of the project work to the guide

Hard copy only / 10 marks

Submission date : 16 th July 2011, Saturday

Content : at least the theoretical aspects


3/35

Interim Report Format

Font Name Times New Roman

Title 18

Sub Heading 16

Paragraphs 12

Paper Size A4

Line Space 1.5 inches


4/35

Chapter 1 Introduction


5/35

Chapter-1 Introduction

Overview of the Project

Name Objective ( Purpose of the project ) Scope Company Profile


6/35

Name of the Project

A good project name helps provide a vision of where the project is headed.

Keep it usable, short. The shorter is the better.


7/35

Objective of the Project

Objectives are the concrete statements Describes the things a project is trying to

achieve. Purpose of the project. It helps frame the project.


8/35

Scope of the Project

The project name is a good place to start. Identify the reason for the project.

It is usually a statement, identifying why theproject is being created. Emphasize the final goal.


9/35

Company profile

Name of the Company Structure of Organization

Nature of Work General Comments/Position in its Industry Referee ( Name, Post, Gender, Education and

Working Experience )


10/35

Chapter 2 System Analysis


11/35

Chapter-2 System Analysis

Existing SystemFeasibility study

Software Requirement Specification

Operational Environment

Software requirement Hardware requirement


12/35

Existing System

This activity relies on knowledge of thehardware, software, workload and monitoringtools associated with the system under study.

Includes the following sub titles, Static Information System Configuration Dynamic Information is extracted from records

produced during system operation


13/35

Feasibility study

It precedes technical development and projectimplementation

The main purpose of the feasibility study is toconsider all factors associated with the projectand other resources will yield a desirableresult.

Involves some usage of available resources.


14/35

Feasibility study

Includes following sub titles, Technical feasibility Economical feasibility Operational feasibility ( User / Top Level

supports )


15/35


Includes the following sub titles, Purpose describes the purpose of the

document Functional Requirements defines the internal

workings of the software. that is, the calculations, data manipulation

and processing, and other specificfunctionality. Business Logic


16/35


Includes the following sub titles, Nonfunctional Requirements performance

requirements, Quality standards, the numberof concurrent users supported, etc


17/35

Operational Environment - Hardware

Component Minimum

Processor 2.5GHz, Name of the processor

RAM 2GB

Disk NTFS file system-formatted partition with a minimumof 3GB of free space

Drive DVD Drive

Network 56 Kbps connection between client computers andserver

Others

** Specify minimum configuration of client and server computers If you use Client / ServerComputing Technology


18/35

Operating System Windows XP Professional Front End Visual Basic.NET

Back End Microsoft SQL Server 2005 Server Apache (Web application) Others Microsoft .NET Framework 3.5

Operational Environment - Software


19/35

Chapter 3 System Design


20/35

Contents

Architecture Design

o Module descriptionso Flow charto Data Flow Diagram (3 levels)

Database Design

o E-R Diagramo Table Design with Constraints

System Design


21/35

System Design

Architecture Design -Module Descriptions

A module description provides detailed

information about the module and itssupported components. Includes the following sub titles,

Module Title and Description Sub Module(s) and Description


22/35

System Design

Architecture Design -Flow Chart

A flow chart is a graphical or symbolicrepresentation of a process.

Each step in the process is represented bya different symbol and contains a shortdescription of the process step.


23/35

System Design

Flow Chart

Architecture

Design -

Flow chart Symbols


24/35

For ExampleEDUCATIONAL RESOURCEMANAGEMENT (Flow Chart)


25/35

System Design

Architecture Design Data Flow Diagram

It is used to how the system transforminformation.

They define how the information process andstored and identified, How the informationflows the process

Where does the data that passes through thesystem come from and where does its go.

What happens the data once it enters thesystem (ie. Input) and before it leaves thesystem (ie.output)

What delays occur in between the inputs andoutputs (ie. Identify the needs for data stored.


26/35

Data Flow Diagram

The above five symbols are used in Data Flow

Diagram (DFD)


27/35

System Design

Level 0 Initially a context diagram is drawn, which

is a simple representation of the entiresystem under investigation.


28/35

System Design

Level 1 The Level 1 diagram; which provides an

overview of the major functional areas of the business.

It also identifies the major businessprocesses at a high level.


29/35


30/35

Level 2


31/35

Level 2


32/35

Level 2


33/35

Database Design E-R Diagrams

An entity-relationship model (ERM) is anabstract and conceptual representation of

data.


34/35

E-R Diagram Example


35/35

Database Design Table Design with Constraints

Table1 : Table Name

Field Name Data type Constraint(s)

Field1 varchar(10)Field2 numeric(4,0) Not Null

Field3 varchar(9)

Field4 numeric(18,0) Primary KeyField5 char(1) Null

Field6 char(1)

Fi ld7 i (18 0) F i K

guidance to interim report 31052011

Documents