table of contents grour member 3 - wordpress.com technology college page 2 physical design ......

Zanzibar Technology College

Table of Contents

GROUR MEMBER ................................................................................................... 3

GROUP MEMBER AND THERE RESPONSIBILITY .............................................................. 3

AKNOLEDGEMENT ................................................................................................. 3

GROUP AGREMENT ................................................................................................ 4

GROUP TARGET ..................................................................................................... 4

CHAPTER ONE .................................................................................................... 5

INTRODUCTION ............................................................................................................................... 5

1.1 Overview ................................................................................................................................... 5

1.2 Problem statement ..................................................................................................................... 6

1.3 The project objective ................................................................................................................. 6

1.4 Justification ............................................................................................................................... 7

1.5 Expected out put ........................................................................................................................ 7

CHAPTER TWO ................................................................................................... 8

LITERATURE REVIEW ................................................................................................................... 8

CHAPTER THREE ............................................................................................... 10

METHODOLOGY ............................................................................................................................. 10

3.1 The system development life cycle ........................................................................................... 10

3.2 System Development Stages Used ............................................................................................ 12

3.3 System/Software Development Model ..................................................................................... 12

3.4 Requirement Analysis ............................................................................................................... 12

3.5 Requirements specification ..................................................................................................... 13

3.6 Scope and Limitations ................................................................................................................ 13

3.7 System user and their task .......................................................................................................... 14

3.8 Use case ....................................................................................................................................... 15

USE CASE ........................................................................................................................................ 17

CHAPTER FOUR ................................................................................................ 23

SYSTEM DESIGNING ..................................................................................................................... 23

4.1 Architecture design ...................................................................................................................... 23

4.2 Conceptual design ................................................................................................................... 24


PHYSICAL DESIGN ........................................................................................................................ 33

CHAPTER FIVE.................................................................................................. 37

IMPLEMENTATION PLAN ............................................................................................................ 37

BUDGET AND RESOURCE FUNDING ......................................................................................... 39

MINUTE OF MEETING ................................................................................................................... 41

5 GROUP MEMBER PARTICIPATION LEVEL .................................................................... 45

CHAPTER SEVEN ............................................................................................... 46

6 CONCLUSION ....................................................................................................................... 46

7 RECOMANDATION ............................................................................................................. 46


GROUR MEMBER

The following are member of this project that consist eight members are as follow

S/N NAME STUDENT ID PHONE NO SIGNETURE

1 Ramadhan Haji S0

2 Bikombo Suleiman Hamad S03172014 +255 777797742

GROUP MEMBER AND THERE RESPONSIBILITY

In this group contain many members who have responsible to work such as the following table below.

AKNOLEDGEMENT

We would like to thanks our God during the process of developing our project started, also our great

full thanks should go to MR Rashid Salim and his assistance for their cooperation and contribution of

helping us to complete this project, and our honest thanks to our fellow students who show their great

talent and time to support our project to be success without forgetting Zanzibar Technology College

members to present their great full contribution of making this project to be amazing and all

stakeholders who gave us good information that are so better on supporting our project to achieve the

project objectives in effectively and efficiently. As group members we should thanks again our head

leader and his assistance to insure that all members from our group must have the enough knowledge

and skills of managing and create the great project by self.

S/N NAME TASK POSITION SIGNETURE

1 Ramadhan Haji Planning MEMBER

2 Bikombo Suleiman Hamad Designing MEMBER


GROUP AGREMENT

The agreements of our group include all activities to our project are as follow;

The group must have a leader who will lead and managing whole project activities.

A member should meet in the discussion four day in the week.

Each member is required to attend 5 minutes before the meeting.

Each participate should contribute what is relevant to the case give and topic that will

discussed during the meeting.

Any member will be cut 5% of his/her marks if he/she will be late for quarter an hour after

meeting start in duration of 5 days.

Any member who will absent in the discussion without massive reason 5% of his/her marks

will be cut.

Any member of the team is to perform any task that he/she will give from a group as an

assignment and to hand it over to the day submitting as planned.

Respect is very important for anyone in the group and each one should be respect idea of a

member.

If there will be financial contribution, all member of the team are to contribute in equal rate, in

order to printing.

Every member must sign of the space signature.

GROUP TARGET

The main aims of our group target to remove all problems that face nursery centers by using new

modern system. The following are the aims of our group target:

The system will enable people to get clearly instruction about nursery.

This system will function for effectively and efficiently to insure that it removes cost, blames

from parents and manage whole nursery.

It removes disturbance for the students who complain about missing group learning and their

result report.

Also it insures that, all members which participate to design this project are increasing their

talent and complete this project on time.

To analyses case study and mention case study.

To meet project as better others made.

To insure that all member get awareness to manage other project by personally.

To insure that all stakeholder happy.


CHAPTER ONE

INTRODUCTION

This project works automatic Nursery Management System. In this system, there are two applications

are developed-Windows based (thick client) and Web based (thin client). Nursery Management

System (NMS) consist main tasks such as registration students, attendance record, keep and control

absentees, producing report cards, producing official transcript, preparing timetable and producing

different reports for teachers, parents and other citizen we need to use. Also it will run automation and

utilization of technology to replace human with a machine that can perform more quickly and more

continuously information.

The windows application takes most of the activities such as offline student registering, transcript and

report card generation, and producing the timetable. The application facilitates attendance recording

by the teachers to view status of students by their parents and to view reports by education.

1.1 Overview

A Nursary Management System (NMS) is the primary system for efficiently operating schools, and

includes applications like, Registration, Enrollment, Attendance, Scheduling ,Grade book and exams,

NMS are centralized systems used by educators and administrators to collect information needed to

manage education delivery, improve student achievement, and ensure accountability

Since NMS are centralized systems, the ministry and schools obtain improved reporting capacity beyond

reports just for individual schools or districts, Robust NMS supports policy changes and new education

delivery methods to achieve the highest student achievement outcomes

These improved information management systems are now required as timely access to data about

student and school performance is critical to achieving education goals, The successful deployment of

NMS is critical for schools to gain full advantage of other education solutions such as learning

management systems and library automation, as these applications rely on student data.


1.2 Problem statement

many students are in waiting list waiting to start and some of them get the chance to join the classes

from any time during the year whenever the chance becomes available. Although this situation allow the

business to grow rapidly but it causes a lot of management problem in such a way that it has get to the

point where it becomes difficult to understand the actual number of students available to the particular

centre at any particular

Time or to have a clear idea of who has started when and finishing at what date.

Additionally, it has also becomes apparent that the management also find difficult to understand the

exactly number of teaching staff are needed for each centre in order to run them effectively and

efficiently. Also there is a growing number of parent’s complaints regarding their children missing

performance records and mixing up levels of learning groups

1.3 The project objective

Main objective

To becomes apparent that the management also find difficult to understand the exactly number of

teaching staff are needed for each center in order to run effectively and efficient also the point

where it becomes difficult to understand the actual number of student available to the particular

center at any particular time or to have a clear idea of who has started when and finishing at that date.

Specific objectives

The following are the various objects that forced group to modernize the nursery information system

To know all the existing and the new coming up established centers with there actually

maximum number of student can handle at any particular time.

To know the actually number of classes or room that each center has.

To know the details of the hand and assistant had of each a system center.

To know the full contact details of every teacher working in a particular existing center.

To know the details of every student, there joining dates, and the level they are in at any

particular time

Want to know exactly the term time (starting and closing time for each year) for each centre.


1.4 Justification

Now days many nursery decided to use computerized system according to the raise helplessly of the

old system in nursery management that lead losing number of students records who has started and

finished, and also it course a lot of parents complaints regarding their children missing performance

records, now we determined to establish the computing system that will work for effectively and

efficiently for ensuring that this system will be going to manage all nursery center since this system it

lead to know all information for each center in nursery management system. Also this computing

system helps the head managers and their assistant to manage all nursery activities and students

records because this system enables them to know how many students are needed to joining in the

nursery in each year in order to remove management problems which facing nursery school that

overpowered nursery to manage each center.

1.5 Expected out put

Nursery management system is base on software computerized system to provide accommodation to

the nursery more efficiently to manage income and outcome in a nursery center, either student or staff.

Also it will store and manipulate the whole information in case of resulting, registration and fee

payment. This system keeps full contact details for each nursery center.


CHAPTER TWO

LITERATURE REVIEW

A Nursery Management System (NMS) is the primary system for efficiently operating schools, and

includes applications like, Registration, Enrollment, Attendance,Scheduling,Grade book and exams,

NMS are centralized systems used by educators and administrators to collect information needed to

manage education delivery, improve student achievement, and ensure accountability

(http://www.sakhr.com/index.php/en/education-platform/school-management-system(15:05:PM))

Nursery management system (NMS) architecture is based on the existence of different modules that are

integrated into a communication protocol. The modularity that characterizes the system, gives great

flexibility and expansion capabilities without undesirable side-effects, since all the changes effect only a

part of the system.

This categorization of these modules depends on the nature of information and the privilege of the user

and it takes place in a way that the modules co-operate as a whole, while on the other hand they preserve

their independence.

http://www.sakhr.com/index.php/en/education-platform/school-management-system(15:05:PM))


]. J. G. Hedberg et. al. (1992). Educational information systems: Problems of the smalleducational

organisation. Australian Journal of Educational Technology, 8(2), 132-

160.http://www.ascilite.org.au/ajet/ajet8/hedberg.html. Time 15:46PM


CHAPTER THREE

METHODOLOGY

Methodology is the step by step approaches followed by a system analyst to develop an information system.

In order to complete our project and to be seen in a better situation, we have used the system development

life cycle.

3.1 The system development life cycle

System Development Life Cycle is the process of developing information systems that effectively use

hardware, software, data, processes, and people to support the company's businesses objectives. SDLC

methodology means combination of various activities and consists of five phases that is:-

Feasibility study

System Planning

System Analysis

System Design

System Implementation.

Feasibility Study: Is an analysis potential of the proposed project which based on exist investigation and

research to support the process of decision making. In order to determine whether or not a given project is feasible,

there must be some form of investigation in to the goals and implication of the project. The project is feasible in

Technical, Economical and Time is as follow.

Technical feasibility

Is the process of determine whether the organization has the technology resources to develop, install

and operate the system. Technical expertise, Computers, software and all necessary tools for project

are available.

Economic feasibility

Is process of evaluating the benefit and the cost of the projects; This means that the benefit must be

grater then cost in order to encourage the owner of the system to agree the system, economic

feasibility means that projected benefits all the proposed system out weight the estimated cost usually

considered the total cost of ownership. The manager of hospital will give all the cost of this project,

thus economic is feasible.

Time feasibility

Schedule feasibility means analyst the time of the project when a project will take how long to

complete, if the time will take too long to the project it will failure. Thus, this project is feasible

because we have enough time to complete.

System Planning: In this phase there are two main activities can be done these are, to identify the needs of

the business and determination of the scope.


System Analysis: The goal of this phase is to determine where the problem is in an attempt to fix the system.

This step involves breaking down of the system in different pieces to analyze the situation, project goals,

breaking down what needs to be created and attempting to engage users, so that definite requirements can be

defined.

System Design: In this phase we are going to discuss about logical design and physical design in order to

complete our design. System Implementation: Is a realization of a technical specification or algorithm as a program, software

component, or other computer system through computer programming and deployment.

Analysis

Design

Plan

Implementation

Fesibility Study


3.2 System Development Stages Used

The adoption of the above methodology in Nursery management System project resulted into blended

methodologies in which various techniques and philosophies from the above methodology were used to

facilitate the analysis, and the development process of the Nursery Management System. The system

development stages followed in this project include:

Investigation of the current manual Nursery management system at Zanzibar Nusery center

System analysis in which investigated requirement ware analyzed hence functional and non-

functional requirement for Nursery management system was obtained.

System Design, which involved logical and physical design of the Nursery management system.

Implementation in which the system was developed.

System Testing and Evaluation where the developed system was tested and evaluated

accordingly.

3.3 System/Software Development Model

Prototyping model was used in accomplishing this project. Prototyping-based methodology performs

analysis, design and implementation phases concurrently and repeatedly. Compared with other system

development methodologies, prototyping has a lot of advantages as it support more users involvement

and enable them to interact with the system before its completion hence get more understanding of the

system and ensure user acceptance.

3.4 Requirement Analysis

Is the study of something that already exists, to answer some questions about it (implications:

something already exists to study; you have questions to ask). That means, the development phase

many software people call "analysis" is not analysis in my mind - in the sense I just mentioned.


3.5 Requirements specification

Perform an analysis of the problem using object-oriented techniques an external view of the enterprise

model of the student registration including student records, department and staff information, course

requirements, and class schedules will be developed using Unified Modeling Language. This System

Requirement Specifications documents will form part of the documentation for the project. Some

desired features of the new system include:

The ability to search/view course offerings on-line

Provide transcripts on-line

Evaluate prerequisites for courses against student records

Inform students of registration stops and provide ability to resolve and registration conflict(s)

Allow students to fill out applications for graduation and plans of study.

3.6 Scope and Limitations

Analysis methodology will involve business analysis, requirement analysis, data analysis, process

analysis, and (web) and application architecture:

Business analysis – State the business rules, business system interfaces, business function,

business ownership, sponsorship and associated project budget requirement

Requirement analysis – System I/O description, user requirement definition, functional and

security requirement

Data analysis – Involve data collection process, data validation, data storage, manipulation and

retrieval

Process analysis – DLC data /process flow analysis, process decomposition and system

interfaces

Application architecture – Analyze application information structure, usability, user interface

design, interaction and application implementation.


3.7 System user and their task

Administrator: refer to system administration, a person who responsible for the performance or

management administrative system operation.

Teacher: is a person who teach something, a person who job is to teach about certain subject

SYSTEM USER TASK

Administrator Will insert student and stuff information and

provide service also will manage the whole

system

Teacher Will insert information from student to

administrator


3.8 Use case

ADMINISTRATOR


TEACHER


USE CASE

Use case Name Add Student

Actor(s) System administrator

Description The use case describes the process of register the information about

the Student

Precondition Actors must login as system admin in order to access this use case

Task Sequence

System administrator will login to the system

System administrator will click add Student button

System will display the form that contain the Students

information to be filling

System administrator will fill the form and click save button

Exception No exception

Post condition The Student information must be saved in the database

Assumption Student is available


Use case Name Add System update



System update


Task Sequence


System administrator will click add system update button

System will display the form that contain the Students

information to be filling



Post condition The update information must be saved in the database

Assumption Student is available


Use case Name Add insert data


Description The use case describes the process of register form into insert data


Task Sequence


System administrator will click insert data button

System will display the form that contain about insert data




Assumption Insert data is available


Use case Name Add Permission


Description The use case describes the process that allow system administrator to

login in the system


Task Sequence


System administrator will insert data

System administrator it allow update and delete data



Assumption permission is available


Use case Name Add Announcement



Announcement


Task Sequence


System administrator will change all announcement of teacher

System administrator will see all announcements.



Post condition The announcement must be saved in the database

Assumption Announcement is available


Use case Name Add Student information



Student


Task Sequence


System administrator will change information about student

System will see all information of Students



Post condition The student information must be saved in the database

Assumption Student information is available


CHAPTER FOUR

SYSTEM DESIGNING

4.1 Architecture design

Nursery management system (NMS) architecture is based on the existence of different modules that are

integrated into a communication protocol. The modularity that characterizes the system, gives great

flexibility and expansion capabilities without undesirable side-effects, since all the changes effect only a

part of the system.

This categorization of these modules depends on the nature of information and the privilege of the user

and it takes place in a way that the modules co-operate as a whole, while on the other hand they preserve

their independence.

Figure 1.0 Architecture of the system


4.2 Conceptual design

Students: Is a person who takes an interest in a particular subject. This table consist many

attributes and address that used to control and manage all students details.

Parents: Is a person who has a child. This table consist all parents who carry their children on

Nursery, in case of understanding school’s fees, result information, and other. This table

creates one to man relationship from parent to student.

Sponsor:Is person who vouches or is responsible for a person or thing.For an infant at baptism,

making the requiredprofessions and assuming responsibility for the child's religiousupbringing

; godfather or godmother.

Staff: Is a group of officers assisting an officer in command of an army formation or

administration headquarters. System will analyze department of staff who responsible for

keeping details of staff. It creates relationship between staff and center.

Brunch: An office of a firm which is located somewhere other than the firm's main

office location. A branch office is simply another location, and is still involved in the business

activities of the firm. More ever this table contains many different brunch of nursery also this

table contain many attribute such as brunch number and location then it create relationship

with student table staff table and room table.

Payment: the action or process of paying someone or something, or of being paid. this table

allow parent to pay nursery fee. That table consist different attributes such as payment number,

payment status and payment amount.

Room: space that can be occupied or where something can be done, especially viewed in terms

of whether there is enough. In a branch have many room that used student for study. this table

create relationship between branch and room

receit:a written acknowledgment of having received, or taken into one'spossession, a specified

amount of money, goods,act the amount or quantity received.the act of receiving or the state of

being received. Something that is received. It will give student after payment.

Student: Is a person who takes an interest in a particular subject. This table consist many

attributes and address that used to control and manage all students details.

Parents: Is a person who has a child. This table consist all parents who carry their children on

Nursery, in case of understanding school’s fees, result information, and other. This table

creates one to man relationship from parent to student.

Staff: Is a group of officers assisting an officer in command of an army formation or

administration headquarters. System will analyze department of staff who responsible for

keeping details of staff. It creates relationship between staff and center.

http://www.businessdictionary.com/definition/office.html

http://www.businessdictionary.com/definition/location.html

http://www.businessdictionary.com/definition/branch.html

http://www.businessdictionary.com/definition/business-activity.html

http://www.businessdictionary.com/definition/business-activity.html

http://www.dictionary.com/browse/receive

http://www.dictionary.com/browse/receive


CONTEXT DIAGRAM


Initial Entity Relationship diagram (E.R.D)

Parent Reciept

Result

Payment

Student

Staff

Sponcer Branches Room

Subject


Resolve Entity Relationship diagram (E.R.D)

ParStudents

*ParentNo

*StudentID

BranchStaff

*StaffID

*BranchNo

Sponsor *ParentNo FirstName LastName Gender Address Email

PhoneNo

Receipt

*ReceiptNo

ReceiptDate

ReceiptAmount

Payment

*PaymentNo

PaymentAmount

PaymentStatus

InvoiceNo

RecsiptNo

Parent *ParentNo FirstName LastName Gender Address Email

PhoneNo

Students

*StudentID

FistName

LastName

Gender

Address

Age

Picture

Level

ParentNo

BranchNo

Rooms *RoomNo

RoomName

BranchNo

Branches *BranchNo Location PhoneNo

Email

Staff *StaffID

FirstName LastName Gender Address

Age Position

BranchNo

Stu/sub

StudentID

Subjectcode

Subject

Subjectcode

Subjectname

Startingdate

enddate

Sub/result

Subectcode

ResultNo

Result

resultNo

marks

teams


Final Entity Relationship diagram (E.R.D)

resultresultNO

term

marks

student_sponsor

student_sponsor

SponserId

StudentId

student_subjectstudent_subject

StudentId

subjectcode

subjectsubjectcode

subjectName

startingDATE

finishingDate

subject_resultstudent_result

resultNO

subjectcode

tbl_branchBranchNo

LocationName

Phone

Email

tbl_branch_staff

tbl_branch_staf...

StaffNo

BranchNo

tbl_parentParentId

FirstName

LastName

Gender

Adress

Age

Email

Possition

tbl_parstudent

ParentId

StudentId

tbl_PaymentPaymentNo

StudentId

PaymentAmount

tbl_ReceiptReceiptNo

PaymentNo

receiptData

receipttime

tbl_RoomRoomNo

BranchNo

RoomName

tbl_SponserSponserId

FirstName

LastName

Gender

Address

Email

Possition

tbl_staffStaffNo

FirstName

LastName

Gender

Address

Age

Qualification

Possition

tbl_studentStudentId

FirstName

LastName

Gender

Adress

[Level]

BranchNo


Entity and attribute

STUDENT

FIELD NAME DATA TYPE SIZE

StudentID Integer -

FirstName Character 10

LastName Character 10

Gender Character 10

Age Integer -

Level VariableCharacter 15

Address VariableCharacter 20

STAFF


StaffID integer -



Gender Character 10

Position Character 20

Age Interger -

Qualification Character 20


BRUNCH


BrunchNo integer -

LocationName Character 30

PhoneNo integer -

Email VariableCharacter 20

ROOM


RoomNo integer -

RoomName Character 15

RECEIPT


ReceiptNo Integer -

ReceiptAmount VariableCharacter 20

ReceiptDate VariableCharacter 10


PARENT


ParentNo Integer -



Gender Character 10



PhoneNo Integer -

Age Integer -

SPONSOR


SponsorNo Integer -


lastName Character 20

Gender Character 20

Age Integer -


PhoneNo Integer -


Position Character 20


SUBJECT

FIELD NAME DATA TAYPE SIZE

SubjectCode Integer -

SubjectName VariableCharacter 30

StartingDate VariableCharacter 50

EndingDate VariableCharacter 40

PAYMENT


PaymentNo Integer -

PaymentAmount VariableCharacter 20

RESULT


ResultNO Integer -

Marks VariableCharacter 30

Terms VariableCharacter 20


PHYSICAL DESIGN

Data manipulation language

Data Manipulation Language (DML) is a family of syntax element similar to a computer programming

language used for selecting, inserting, deleting and updating data in data base. Performing read-only

quire of data in some times also considered a component of DML. (Data Manipulation means

including related links, information and term)

Creation command that used to design a database in table

create database NMS;

go

create table tbl_branch( BranchNo int identity (1,1)not null,

LocationName char(30)not null,

Phone int not null,

Email varchar (20)null,

constraint pk1 primary key (BranchNo)

);

create table tbl_staff(

StaffNo int identity (1,1)not null,

FirstName char(10)not null,

LastName char(10)not null, Gender char(10)not null,

Address varchar(20)not null,

Age int, Qualification char (20)not null,

Possition char (20)not null,

constraint pk2 primary key (StaffNo)

);

create table tbl_branch_staff(

tbl_branch_staffID int identity (1,1)not null,

StaffNo int, BranchNo int,

constraint pk3 primary key (tbl_branch_staffID),

constraint fk1 foreign key(StaffNo)references tbl_staff(StaffNo),

constraint fk2 foreign key(BranchNo)references tbl_branch(BranchNo)

);

create table tbl_Room(


RoomNo int identity(1,1)not null,

BranchNo int not null,

RoomName char (15),

constraint pk4 primary key (RoomNo),


);

create table tbl_Sponser(

SponserId int identity (1,1)not null,


LastName char(10)not null,

Gender char(10)not null,

Address varchar(20)not null,



constraint pk5 primary key (SponserId)

);

create table student_sponsor(

student_sponsor int identity(1,1)not null,

SponserId int,

StudentId int,

constraint pk13 primary key(student_sponsor),

constraint fk5 foreign key(SponserId)references tbl_Sponser(SponserId),

constraint fk13 foreign key(StudentId)references tbl_student(StudentId)

);

create table tbl_student(

StudentId int identity (1,1)not null,




Adress varchar(20)not null,

Level varchar(15)not null,

constraint pk7 primary key (studentId),

BranchNo int not null,


);


create table tbl_parent(

ParentId int identity (1,1)not null,




Adress varchar(20)not null,

Age int,



constraint pk8 primary key (ParentId)

);

create table tbl_parstudent(

ParentId int not null,

StudentId int not null,

constraint fk7 foreign key(ParentId)references tbl_parent(ParentId),

constraint fk8 foreign key(StudentId)references tbl_Student(StudentId)

);

create table tbl_Payment(

PaymentNo int identity(1,1)not null,

StudentId int,

PaymentAmount varchar(20)not null,

constraint pk10 primary key (PaymentNo),

constraint fk9 foreign key(StudentId)references tbl_Student(StudentId)

);

create table tbl_Receipt( ReceiptNo int identity (1,1),

PaymentNo int not null, receiptData char(20)not null,

receipttime varchar(10)not null,

constraint pk11 primary key (ReceiptNo),

constraint fk11 foreign key(PaymentNo)references tbl_Payment(PaymentNo)

);

create table result(

resultNO int identity(1,1)not null,

term varchar(15)not null,

marks varchar(15)not null,

constraint pk16 primary key(resultNO)

);

create table subject_result(

student_result int identity(1,1),

resultNO int,

subjectcode int,

constraint pk17 primary key(student_result),


constraint fk16 foreign key(resultNO)references result(resultNO),

constraint fk17 foreign key(subjectcode)references subject(subjectcode)

);

delete result;

drop table result

.................................NEW...............................................

create table subject(

subjectcode int not null identity (1,1),

subjectName varchar(17)not null,

startingDATE varchar(21)not null,

finishingDate varchar(21)not null,

constraint pk18 primary key(subjectcode)

);

create table student_subject(

student_subject int not null identity (1,1),

StudentId int,

subjectcode int,

constraint pk19 primary key(student_subject),

constraint fk18 foreign key(StudentId)references tbl_student(StudentId),

constraint fk19 foreign key(subjectcode)references subject(subjectcode)

);


CHAPTER FIVE

IMPLEMENTATION PLAN

Is a management tools design to illustrate, in details the critical steps in developing and starting a

project. It is guide or map that help programs stuff to be proactive rather than reactive in developing

their programmer and identifying any challenges along the way.

INITIAL GANG CHAT

Initial Gantt chart is the Gantt chart that shows all planning of project from beginning up to End of

the project. The table below show the expectation date of activities, start date, duration and the end

date.

Activity Start date Duration End date

Planning 8/5/2016 10 8/14/2016

Feasibility study 8/15/2016 12 8/26/2016

Analysis 8/27/2016 13 9/8/2016

Design 9/9/2016 11 9/19/2016

Implementation 9/20/2016 8 9/27/2016

Testing 9/28/2016 7 10/4/2016

Maintenance 10/5/2016 9 10/13/2016

Finalizing 10/14/2016 12 10/25/2016

Submission 10/26/2016 1 10/26/2016


UPDATE GANG CHAT

Updated Gantt chart is the Gantt chart occurs in middle of the project update from initial Gantt chart.

The table bellow shows the project activities, start date, duration, remaining days and end date.

Activity Start date Complete Remain day End date

Planning 8/5/2016 10 0 8/14/2016

Feasibility study 8/15/2016 12 1 8/26/2016

Analysis 8/27/2016 13 2 9/8/2016

Design 9/9/2016 11 4 9/19/2016

Implementation 9/20/2016 8 1 9/27/2016

Testing 9/28/2016 7 2 10/4/2016

Maintenance 10/5/2016 9 3 10/13/2016

Finalizing 10/14/2016 12 5 10/25/2016

Submission 10/26/2016 1 0 10/26/2016

FINAL GANG CHAT

Final Gantt Chat is Gantt Chat occurs at the end that shows clear planning project up to completed.

The table below shows the project activities, Start date, complete days and End Date.

Activity Start date Complete End date


Planning 8/5/2016 10 8/14/2016

Feasibility study 8/15/2016 12 8/26/2016

Analysis 8/27/2016 13 9/8/2016

Design 9/9/2016 11 9/19/2016

Implementation 9/20/2016 8 9/27/2016

Testing 9/28/2016 7 10/4/2016

Maintenance 10/5/2016 9 10/13/2016

Finalizing 10/14/2016 12 10/25/2016

Submission 10/26/2016 1 10/26/2016

BUDGET AND RESOURCE FUNDING

In this project contains many activities in order to meet requirement and successful. The following table

shows the barged that used to buy the resources

S/N REQUIREMENT QUANTITY UNITS TOTAL AMOUNT

1 Programmer 3 500000 1500000

2 Analysts 2 1000000 200000

3 Designer 3 800000 2400000

4 Computer 5 300000 1500000

5 Saver 1 1000000 1000000


6 Printer/Scanner 1 800000 800000

TOTAL COST

10000000

Budget

The project will be cost about

10000000

Balance budget of our project is 2600000


MINUTE OF MEETING

FIRST MEETING

Started on 27th

July 2016 at Zanzibar Technology College in lecture Room, started at 1:00pm up to

3:00pm

S/N NAME ATTENDANCE TASK ALLOCATION SIGNATURE

1 Bikombo Suleiman Hamad Present Acknowledgement

2 Ramadhan Haji Present Introduction

Topic discussed: Project planning

Report: successful

SECOND MEETING

Started on 1stAugust 2016 at Zanzibar Technology College in Lab Room, started at 1:00pm up to

3:00pm


1 Ramadhan Haji Present Project objective

2 Bikombo Suleiman Hamad Present Requirements

Topic discussed: continue Project planning

Report: successful


THIRD MEETING

Started on 4th

August 2016 at Zanzibar Technology College in Lab Room, started at 1:00pm up to

3:00pm


1 Ramadhan Haji Present Initial ER Diagram

2 Bikombo Suleiman Hamad Present Methodology

Topic discussed: Analysis and Design

Report: successful

FOURTH MEETING

Started on 8th


3:00pm


1 Ramadhan Haji Present Initial ER Diagram

2 Bikombo Suleiman Haji Present Methodology

Topic discussed: Analysis and Design

Report: successful


FIFTH MEETING

Was starting on1 4th

August 2016 at Zanzibar Technology College in Practical room, started at 1:00pm

up to 3:00pm


1 Bikombo Suleiman Hamad Present Final ER Diagram

2 Ramadhan Haji Present Conceptual design

Topic discussed: Relationship, Conceptual and physical design

Report: successful

SIXTH MEETING

It started on 16th

August 2016 at Zanzibar Technology College in Diploma Room, started at 12:00pm

up to 2:00pm


1 Bikombo SuleimanHamad Present Final ER Diagram

2 Ramadhan Haji Present Conceptual design

Topic discussed: was going on Relationship, Conceptual and physical design

Report: successful

SEVENTH MEETING

It started on 17th

August 2016 at Zanzibar Technology College in Certificate Room, started at 12:00pm

up to 2:00pm


1 Ramadhan Haji Present Implementation plan

2 Bikombo Suleiman Hamad Present Initial gang chat

Topic discussed: implementation plan an how to create gang chat

Report: successful


EIGHTH MEETING

It started on 18th

August 2016 at Zanzibar Technology College in Diploma Room, started at 12:00pm

up to 2:00pm


1 Ramadhan Haji Present Update gang chat

2 Bikombo Suleiman Hamad Present Final gang chat

Topic discussed: update and final gang chat

Report: successful

NINTH MEETING

It started on 24th


2:00pm


1 Ramadhan Haji Present Designing

2 Bikombo Suleiman Hamad Present Formatting

Topic discussed: Formatting and designing

Report: successful

FINAL MEETING

It started on 26th


2:00pm


1 Ramadhan Haji Present Print and submission

2 Bikombo Suleiman Hamad Present Print and submission

Topic discussed: About Printing and submitting project

Report: successful


5 GROUP MEMBER PARTICIPATION LEVEL

The table below shows the participation level for each member of this project

NAME STUDENT ID PARTICIPATION LEVEL

Ramadhan Haji 99%

Bikombo Suleiman Hamad S03172014 99%


CHAPTER SEVEN

6 CONCLUSION

Obviously, project has much information in a real society because it enables a particular management

to manage its facility in a special accepted system. It makes the manager to manage their facilities

records, such as how many teachers are on their facility, how many students are school, their

performance and failure. Project enables a manager to be alert on what has done wrong at a past time

as challenges to make changes on a management. The system must also gives a message alert that used

to remained for expire date of each student and staff. After system being changed include the

management will help staffs to do well in efficiently and organization at all. Organization will be

between staffs and students that will make students to work hard on their studies. Project participation

ensures that every member of the group to get skills and knowledge to understand his/her own on how

to create and applying chances on doing project.

7 RECOMANDATION

We suggest this system to non automatically, also this system needs educated person who have full

experience knowledge to using this system during the creation of this project we failed with different

challenges such as to communicate each other according to leak of technology equipments example

smart phone, laptop and network due to this problem course task to delay in our project even though

but is not obstacle to make our project to deliver on time.

table of contents grour member 3 - wordpress.com technology college page 2 physical design ......

Documents