ASSIGNMENT - MARKING SCHEME

TECHNOLOGY PARK MALAYSIA

CT046-3-2-SDM

SYSTEM DEVELOPMENT METHODS

NP2F1901IT

HAND OUT DATE: 3 FEBRUARY 2019

HAND IN DATE: 10 MAY 2019

WEIGHTAGE: 50%

INSTRUCTIONS TO CANDIDATES:

1 Submit your assignment at the administrative counter.

2 Students are advised to underpin their answers with the use of

references (cited using the Harvard Name System of Referencing).

3 Late submission will be awarded zero (0) unless Extenuating

Circumstances (EC) are upheld.

4 Cases of plagiarism will be penalized.

5 The assignment should be bound in an appropriate style (comb

bound or stapled).

6 Where the assignment should be submitted in both hardcopy and

softcopy, the softcopy of the written assignment and source code
(where appropriate) should be on a CD in an envelope / CD cover
and attached to the hardcopy.

7 You must obtain 50% overall to pass this module.

 GROUP ASSIGNMENT
CT046-3-2 SDM
SYSTEM DEVELOPMENT METHODS
Submitted By:
Niroj Thapa (NP000199)
Prashil Khadka (NP0000202)
Sonam Rinzing Tamang (NP000207)

Submitted To :
Mr. Rabi Rauniyar
 Acknowledgement
The given assignment of System Development Methods is on the management of E-
Smart Kid: Kindergarten Management System and its resources.
Currently the administrative staffs are responsible to handle all the data related to
students, teachers as well as class schedules and all the data are stored using
spreadsheet. The Kindergarten Management System is developed to support the daily
operations of the Kindergarten by the help of computerized system. Before the system
was developed the management of kindergarten was done manually with the help of
spreadsheet which had a lot of disadvantages. As the number of data increase, it is
hard to organize and keep track of the data that results in data redundancy which leads
to data duplication and poor security. This is because all the data are stored manually.
Thus the Kindergarten Management System is developed and had become much
easier for the data record and retrieval.

Lastly, we would like to show gratitude to the whole operation and management team.
The efforts that whole team have shown is appreciable. Also we would like to express
deepest gratitude to our lecturer, Mr. Rabi Rauniyar without whom this management
system would not have been completed.
Sincerely Yours’
Niroj Thapa
Prashil Khadka
Sonam Rinzing Tamang
 Executive Summary
As per the assessment, we are to create a web application for Smart Kid Kindergarten
currently situated in Hartamas, KL in Malaysia to overcome the data management
regarding the students, schedules and resources of the kindergarten. The kindergarten
features resources such as the swimming pool, sand pit, water wall, art & dance
studio, garden, hotel and pet corner. The kindergarten features several development
programs to ensure physical, cognitive, social and personal development for 100
children ranging from the age of 3-4 years (pre-kindergarten) on PK/2017 intake and
5-6 years (pre-school students) on PS/2017 intake in the current year.
In this assumption, we, the Professional IT Pvt. Ltd., are hired by the kindergarten to
create a prototype: E-Smart Kid: Kindergarten Management System, a web
application that will be operated by the organization’s administration and the staffs.
The web system to be developed by the team now has to manage several activities of
the kindergarten such as attendance system, staffs as well as the schedules: exercise,
breakfast, study hours, lunch and the playtime schedules. Currently, the activity and
data management is done manually thus, hard to record and apply in the kindergarten.
After the development of the system, all the daily activities can run smoothly by using
a systematic computerized management system.
The system is to be created by using agile management system by implementing the
agile principles and its methodologies for the development work. Here we prepared
the report on distinctive information about the agile principle and its methodologies
with the comparison of different methods. We hope our application software will help
in the aspects of the kindergarten management as it also helps to reduce the workload
of the staffs.
Table of Contents

1. Introduction to Project Planning................................................................................1

1.1 Introduction to our company................................................................................1
1.2 Scope, Aim and Objective....................................................................................2
2. Agile Principle and IS Methodologies.......................................................................3
2.1 Agile Principles....................................................................................................3
2.2. IS Methodologies................................................................................................6
2.3 Individual Assignments:.......................................................................................7
Individual Assignment (SCRUM: Sonam Rinzing Tamang).....................................8
Individual Assignment (Prashil Khadka: Kanban)..................................................12
Individual Assignment (Extreme Programming: Niroj Thapa)...............................16
Waterfall Methodology:...........................................................................................21
3. System Analysis.......................................................................................................22
3.1 Requirement Elicitation.....................................................................................22
3.2 Data Analysis.....................................................................................................23
3.3 Data Presentation:..............................................................................................24
4. System Design..........................................................................................................25
4.1 USE CASE DIAGRAM (Behavioral UML) :....................................................27
4.2 CLASS DIAGRAM (Structural UML):.............................................................28
4.3 DATA FLOW DIAGRAM (Data flow UML):..................................................29
4.4 Physical designs: Frames...................................................................................30
5. Implementation and Deployment.............................................................................34
5.1 Construction.......................................................................................................34
5.3 System Deployment...........................................................................................39
6. Conclusion................................................................................................................41
Reference......................................................................................................................42
Appendix:.....................................................................................................................44
Gantt charts:.............................................................................................................44
Table of Figures
Figure 1 Logo of the company.......................................................................................1
Figure 2: IS Methodologies in the development............................................................7
Figure 3: Scrum Methodology.......................................................................................8
Figure 4: Scrum Requirements.....................................................................................10
Figure 5 Kanban cards and board................................................................................12
Figure 6 Kanban board in Smart-Kid: Kindergarten Management System.................15
Figure 7 Extreme Programming...................................................................................16
Figure 8: Waterfall Method..........................................................................................21
Figure 9: Data Presentation Methods...........................................................................24
Figure 10 Activity Diagram for E-Smart Kid: Kindergarten Management System....27
Figure 11: Class Diagram for E-Smart Kid..................................................................28
Figure 12: DFD for E-Smart Kid.................................................................................29
Figure 13: Home Page Design.....................................................................................30
Figure 14: Login Page..................................................................................................31
Figure 15: Admin Page Design....................................................................................32
Figure 16: Academic Staff Page design......................................................................33
Figure 17: Tools for E-Smart-Kid................................................................................36
Figure 18: Group Gantt Chart......................................................................................44
Figure 19: Individual Gantt Chart: Niraj Thapa...........................................................45
Figure 20: Individual Gantt Chart: Prashil Khadka.....................................................45
Figure 21: Individual Gantt Chart: Sonam Rinzing Tamang.......................................46
1. Introduction to Project Planning
1.1 Introduction to our company
The Professional IT Pvt. Ltd is a reputed company that contributing in the
development of applications and systems as well as specializing in serving expert
solutions in web-hosting, security to the need and demand of the clients. The
Professional IT has maintained solid relationships with its clients and has continued to
develop innovative solutions for our client over nations since its establishment in
2017 and looks forward to serve its loyal clients in the upcoming years.
Professional IT has been dealing with over thirty satisfied companies nationally and
internationally including companies in India, Bhutan, Sri-Lanka and Malaysia ,
accommodating various sectors like healthcare, marketing, web hosting, E-business,
communication and data security with over hundreds of projects just in the recent two
years since its establishment.

Figure 1 Logo of the company

Our company has developed a prototype for E-Smart Kid: Kindergarten

Management System, a web application system for the management of data activity
and resources for Smart Kid Kindergarten. The web application system promises in
following business processes and agreements for complete features, data security and
access; only by authorized personal. As described before the honor of maintaining the
business flow and timely delivery is one, our company prioritizes. The business
process work flow is to be maintained as per the agreements. The teams will be
developing the prototype system that include web pages, hosting, data base

1
management, trainings, system development and training and assistance for the
kindergarten.
1.2 Scope, Aim and Objective
The proposed system is E-Smart Kid: Kindergarten Management System for
Smart kid private kindergarten. The current system is manual and hard to work with.
The main intention of this system is to reduce the workload.
The Professional IT has following aims and scopes for the current prototype
application:
Scope of the company on E-Smart Kid: Kindergarten Management System:
The activities and the functions specified are included in the project to ensure that the
system has no incompletion.
Professional IT Pvt. Ltd envisions achieving the following scopes:
 Protecting the honor of the system with complete features
 Fulfilling Smart-Kid product that is computable.
 Confirming the agreements between the client and the company of the project
completion.
 Establishing practicality on physical and functional designs and use.
 Making sure the product is delivered on time.
As for the “E-Smart Kid: Kindergarten Management System” the main aim is to
record the data of the students in a digital format so that the record are safe, non-
redundant and easy accessible.
The main objective of this system is to reduce the workload as well as improvise the
working system where most of tasks are still done manually in files or spreadsheet.
The aim and objectives of creating the system are as follows:
 To ensure return the product for what you paid.
 To make sure the quality in security, database and functions.
 To deliver the performance at its best on application on recording.
 To fortify easy technology and access on features with security on
information.
 To deliver fulfillment the business rules of the project to record, retrieve,
manage and protect its components and resources.
 To protect agreement of the objectives, finance, rules, security and
performance of E-Smart Kid.

2
2. Agile Principle and IS Methodologies
Agile method is a specific technique or approach for system management that helps in
programming advancement and fast project completion. This strategy is finished in
groups and breaking project into little bits of client usefulness called client stories,
organizing them, and after that constantly conveying them in short two week cycle.
Coordinated technique for the most part utilizes iterative work arrangements that are
regularly called as dashes. [ CITATION CLa17 \l 1033 ]

2.1 Agile Principles

The agile manifesto or agile mindset is the new style of creating software replacing
the old systems of traditional techniques. The agile manifesto, 2001 by seventeen
independent-minded software practitioners defines its twelve principles as follows:

 Customer satisfaction by early and continuous delivery of valuable

software
Customer satisfaction is important for the smooth and advancement of the
company. It is vital process to deal with costumer and deliver the system
accordingly. Kindergarten Management System very much in need to the
school in time and their satisfaction is our first priority by delivering before
dateline and provide continuous delivery of valuable products iteratively and
incrementally.
 Deliver working software frequently, from a couple of weeks to a couple
of months, with a preference to the shorter timescale.
Delivering software time and again can enhance the productivity and viability
of the application creating. . This principle concentrates more on making the
application and save time.
 Welcome changing requirements
Costumer is always welcome to change their requirement of product before
the project is advancing to the next phases. Frequent meeting between
developer and client will be effective to get their feedback about the progress.
 Build projects around motivated individuals.
Give costumer the environment and support they need, and trust them to get
the job done accordingly in time. Provide a comfortable environment of

3
 workplace and good quality of product show encouragement to the team and
the costumer.
 Face to face conversation is the best form of communication
The most efficient method of conveying information to and within a
development team is face-to-face conversation. This principle is important as
it encourage open communication among the team members and the customers
in terms of meeting requirements.
 Working software is the primary measure of progress.
As objectives the principle implies that the application should be useable with
full functioning and delivered to the end user at time. The program should also
be successfully tested. For instance, diversions office measures the
advancement by separating the assignments into littler parts and dispersed
appropriately to individuals from the groups. This will guarantee that each
assignment can be finished by the given dateline and it is simpler approach to
gauge.
 Continuous attention to technical excellence and good design enhance
agility.
For long term and sustainability of the project continuous attention to
excellence technical and design is essential. We certainly need to pay attention
to and prioritize good design and architecture otherwise it will certainly kill
the project down the line or at least restrain our ability to deliver often.
 Simplicity- the art of maximizing the amount of work not done – is
essential.
This principle focuses on the simple and user friendly of the software so that
costumer can easily use. The extra focus on this principle does help the team to
be careful of the decisions they make. Mastering this skill can improve the
team agility and produce better results.
The best architectures, requirements, and designs emerge from self-
organizing teams.
 At regular intervals, the team reflects on how to become more effective,
than tunes and adjust its behavior accordingly.

4
The above agile principles are the most commonly used principles in a project. As
principles they are summarized into four important points that states the agile
principle which are:

 Customer Satisfaction
 Teamwork
 High Product Quality
 Fast Development

5
2.2. IS Methodologies
Agile Methodology is an advancement technique in which necessities and
arrangements develop in cross-practical groups through the collective effort. Its
methodology adjusts venture and item improvement to prerequisites of the client and
by and large organization objectives on iterative advancement. The information
systems methodologies are those strategies that help to finish a task quicker alongside
building up a higher quality project. This procedure empowers visit assessment and
adjustment which helps in quick conveyance of superb programming. [ CITATION
Gra17 \l 1033 ]
A few examples of IS Methodologies that utilizes agile principle for the project
improvement are as per the following:
 Extreme Programming (Xp).
 Scrum Agile Modeling Adaptive Software Development (ASD).
 Dynamic Systems Development Methods (DSDM).
 Lean software development.
 Feature driven software development.
 Kanban
As agile and IS methodologies are the most significant strategies to build up an
administration system, the techniques are simple, adaptable and reasonable for all
kind of models for the administration system. The organized systems that are
prevalent for the project development are as per the following:
 Waterfall
 SSADM
 V-model
The agile method pursue the agile principle for the improvement of the software or a
task which are easy to utilize yet hard to complete. There are the two merits just as the
d-benefits of utilizing the agile methodologies. The advanced period workplaces
regularly utilize structured techniques and old one utilize the structured method. As
agile is fast growing procedure for the project development a portion of the normal
focal points of the agile principle are enlisted underneath as:
 Agile methods allow two way communications between clients as working
team.
 Agile emphasize on the use of latest tools and technology.

6
 Agile methodologies are faster methods for project development than
structured methods.
 The project development focuses mostly customer satisfaction.

7
2.3 Individual Assignments:
For the development of the project the selected methodologies are compared and
distinguished as follows :

Figure 2: IS Methodologies in the development

8
The above agile IS methodologies that are used in the development process to create
the E-Smart Kid: Kindergarten Management System. The methodologies and their
uses are described individually below:

9
Individual Assignment (SCRUM: Sonam Rinzing Tamang)

Scrum is a framework that helps in team work which encourages team to learn
through experiences, self-organize while working on a problem solving process, and
reflection on theirs win and losses to continuously improve. Scrum is gradual and
quantitative agile programming advancement strategy for programming undertakings
and item or application improvement. Scrum is utilized for project with objective of
conveying new programming software ability every 2 weeks to a month.

Figure 3: Scrum Methodology

Why is scrum necessary for kindergartens Management System?

It controls process that slices through complex nature to concentrate on building
programming software that addresses business issues. It is most frequently used by
software development teams, its principles and lessons can be applied to all kinds of
teamwork. Often thought of as an agile project management framework, Scrum
describes a set of meetings, tools, and roles that work in concert to help teams
structure and manage their work.

10
 Advantages of Scrum Methodology in Kindergarten Management System
 Agile scrum helps in saving time and money.
 Due to short sprint and constant feedback, it is easier to cope with the changes.
 Iterative in nature as it requires constant feedback.
 Delivery of products at constant time. No delay in delivery.
 Overhead cost in process management is minimal leading to quicker and
cheap results.
 Receives higher customer satisfaction.
There are three primary roles in scrum methodology and they include:  Product
owner, Team member and Scrum master;
 Product owners relate vision of the product to the development team and stand
in customer interests through requirements and prioritization
 Scrum masters behave as a connection between the team and the product
owner. Their main aim is to remove any blockade that may prevent the team from
reaching its set goals. Scrum masters help the team to remain creative and productive.
 Scrum teams usually comprise seven cross-operational members. For example,
software projects have analysts, software engineers, architects, programmers, UI
designers, QA experts and testers.
Scrum teams also involve stakeholders and managers besides the major roles. These
players don’t have any official roles in the scrum and are involved in the process only
once in a while. Their roles are often known as subordinate roles.
The scrum methodology has three main art effects which are:
 Product Backlog: This is a high-level list maintained throughout the entire
project. It is used to join backlogged items.
 Sprint Backlog: This contains the list of work the team needs to carry out
during the successive sprints. The features are broken down into tasks, which are
normally between four and 16 hours of work.
 Burn Down: This chart shows the remaining work in the sprint backlog. It
provides a simple view of progress of sprint and is updatable every day.
Scrum is a feedback-based empirical methodology which is, like all empirical process
control approaches, supported by the three foundations of Inspection, Transparency
and Adaptation. These three foundations require openness and trust in the team, which
these five values of Scrum support.

11
 Openness
Members of the team and their stakeholders consent to be open about their work and
any issues they encounter.
Commitment
Members of the team individually promise to reach their team goals, in every Sprint.
Courage
Team members know they are courageous to work through disagreement and issues
together so they can do what is right.
Respect
There is respect among team members to be capable technically as well as to work
with the right intent.
Focus
Members of the Team concentrate exclusively on the goals of their team and the
Sprint Backlog; no work should be done outside their backlog.

Figure 4: Scrum Requirements

DISADVANTAGES OF SCRUM AGILE SOFTWARES

 Without a clear definition, it becomes difficult for the scrum master to plan,
structure and organize a project that lacks clear definition.
 Scrum is a small team in an organization and if the team members are not
active enough to work together or are not committed then there can be a loss to
finishing the organizational goals and also chances for project failure.
 Sprint relentlessly follow each other in rapid succession and might lead to
burn out.

12
WHAT ALL IS INVOLVED IN AGILE SCRUM? ( Methodology )
Scrum Master: Acts as a facilitator of the product owner and the team. The scrum
master helps remove the difficulties that come across the team in achieving the
organizational goals. This will help the team in being active and making sure that the
work is being reported visibly to the project manager.
Prioritization of tasks: The scrum master looks after the working of the employees
in the team. As the team works together, easiness and proper prioritization of the work
will be delivered at the correct time. The scrum model seeks daily scrums as the way
to synchronize the work of the team members as they have to discuss the work of the
sprint.
 Daily Scrum Meeting: All team members should attend the meeting on daily basis
including the Scrum Master and the product owner. This is the meeting which has a
fixed time not more than 15 minutes and it basically deals with the task that they have
to do, will do and identifies any impediments to the progress.
Review of the work: The team conducts a sprint review during which the team
derives the new functionality to PO or any other stakeholders that can provide reliable
feedback that can improve the functionality of the sprint goals.
This feedback loops with scrum software development which may result in the
changes to the freshly delivered functionality but likely to result in revising or adding
items to the product backlog.

13
Individual Assignment (Prashil Khadka: Kanban)

Kanban is a Japanese term meaning billboard or card. Kanban is a word used to

describe any visual any that triggers a relative action. Like the word itself, Kanban
methodology as an IS method is a technique used to help organized and improved
product manufacturing by the means of visual signboards for triggering process for
services and production. Kanban technique was originated in Japan, introduced by
Toyota in 1950s for manufacturing cars developing now to be used in architecture,
construction, software development and personal time and resource management.
Kanban is a simple but powerful tool that can help business owners, developers and
project managers stay organized.

Figure 5 Kanban cards and board

How it is used?
The Kanban System helps in maintaining collaboration within the team with well-
informed. Kanban System alongside good participation eliminates loss of resources
and does not have the requirement of long reports due to step by step flow in work.
The basic requirement for the Kanban system is the Kanban board. A Kanban board is
consists of four columns: back log, to do list, in progress and the completed tasks.
Activities are texted or sketched in a card which travels in the row from backlog and
to do list towards the completed. These cards are often called stories, since they define
tasks in a sequence that needs to start from its small generation that gradually goes
through lots of work until its completion. The back log contains heap of uncompleted

14
tasks and activities that needs dealing with. It is then listed by importance of the tasks
that are thought of and is not yet finalized in the back log. Then initialized the tasks
are first kept in the to-do list which is passed towards the in progress amidst its
completion and finally send to completed lists either in a Kanban board crated
virtually or physically.
This way, the flow of the tasks travels starts from its initial birth to its completion.
After the creation of the board, tasks are separated to different necessary task
contributors to encounter and assure the fulfillment of respective tasks. After the tasks
are separated participators are assimilated in different groups to separate group of
tasks with sub tasks. E.g: Design task is separated into subtasks and then divided to
respective contributors so goes with developers, artists, typist and creative team. A
typical Kanban is applicable for all types of products ranging from small business as
miniature application development to large organizations such as in big software
development.
Advantages of Kanban:
Kanban has many advantages due its way of working of flowing tasks in divisions.
Some of the few are listed below:
a. Flexibility:
Kanban method is flexible in project processing. The absence of constant
durations in sub-phases in relative tasks has advantage on its own to be able to
modify in process such that the products can be stretched and worked out to
different a constraints and cover various attributes.
b. Focused team:
Kanban keeps team focused with tasks divisions relying on the departments
and skills. The tasks are drawn to cover minimum requirements such that it
does not affect the work and create tenacious halts. Team can work with
flexible ideas in need awhile focusing on the sub-divided tasks.
c. Productive:
Kanban relies on working on flexibility and low wastes such that the team can
brainstorm on productive ideas and implementation techniques in order to
uniqueness in products. The divided team has relative divisions and sub
divisions on task such that the team can focus on individual phases with
willingness to check and develop according to needs and distinctive product
ideologies without crossing over the principles of agile management.
15
 d. Efficient:
Coherent development of the product is one of the features of using the
Kanban system. It is methodological and ordered in a flow such that the tasks
are ensured in completion phase by phase, depending upon the nature of the
relative tasks.
e. Continuity in delivery:
Kanban gives continuity in work flow of phases of the project. With the sub
division in the tasks, the delivery of portions in the product is easy and
synchronizing them relatively to departmental tasks is ensured. Kanban makes
the best of use time and opportunity with compatible objectives and values
delivery in time. In case, of system and human faults the automation makes
continuity in efficient deliverance.
f. Waste Reduction:
Reducing the waste in resources is one of the major motives of using the
Kanban system. The team focuses on maintaining production scale, deficiency
in projects, time reduction, using the manpower on its fullest while keeping
the delivering the complete product with minimized waste insight. The method
ensures replacing the time spent on incorrect and invaluable tasks with work
with correct and more valuable work.
Disadvantages of Kanban:
Kanban is easy to maintain but conditional demerits comes with results that affect the
production process in Kanban. The disadvantages of Kanban in varying conditions are
listed
a. When the product is in very large scale with various production types,
handling the production scale is difficult.
b. When the flow is halted, the next task in progress is halted as well.
c. Frequent changeovers require increment in finance and adjustments.
d. Slow flow causes slow production.

16
Kanban in the current project development:
In the current system development we had to an agile system development method.
Individually, I selected Kanban for E-Smart kid due to its properties of waste
reduction and flexible task handling. The tasks are separated into different divisions
and ideas in order to create Kanban cards and divide them into different departments
to accomplish the final products:

Figure 6 Kanban board in Smart-Kid: Kindergarten Management System

The above representation of the Kanban board shows the development of project in
creating the system. Back logs were first to create ideas required to develop the
ongoing processes and then followed by the departments to create the complete
system in a flow.

17
Individual Assignment (Extreme Programming: Niroj Thapa)

Extreme Programming (XP) is an agile software development framework that aims to

produce higher quality software, and higher quality of life for the development team.
XP is the most specific of the agile frameworks regarding appropriate engineering
practices for software development[ CITATION agi19 \l 1033 ].

Figure 7 Extreme Programming

When Applicable

The general characteristics where XP is appropriate were described by Don Wells

on www.extremeprogramming.org:

 Dynamically changing software requirements

 Risks caused by fixed time projects using new technology
 Small, co-located extended development team
 The technology you are using allows for automated unit and functional tests

Due to XP’s specificity when it comes to its full set of software engineering practices,
there are several situations where you may not want to fully practice XP. The
post When is XP Not Appropriate on the C2 Wiki is probably a good place to start to
find examples where you may not want to use XP[ CITATION agi19 \l 1033 ].

18
You can’t use the entire XP framework in many situations, but that shouldn’t stop you
from using as many of the practices as possible given your context.

Basic principles of Extreme programming

XP is based on the frequent iteration through which the developers implement User
Stories. User stories are simple and informal statements of the customer about the
functionalities needed. A User story is a conventional description by the user about a
feature of the required system. It does not mention finer details such as the different
scenarios that can occur. Based on User stories, the project team proposes Metaphors.
Metaphors are a common vision of how the system would work. The development
team may decide to build a Spike for some feature. A Spike is a very simple program
that is constructed to explore the suitability of a solution being proposed. It can be
considered like a prototype[ CITATION gee19 \l 1033 ]. Some of the basic activities
that are followed during software development by using XP model are given below:
 Coding: The concept of coding which is used in XP model is slightly different
from traditional coding. Here, coding activity includes drawing diagrams
(modeling) that will be transformed into code, scripting a web-based system and
choosing among several alternative solutions[ CITATION gee19 \l 1033 ].
 Testing: XP model gives high importance on testing and considers it be the
primary factor to develop fault-free software.
 Listening: The developers need to carefully listen to the customers if they must
develop a good quality software. Sometimes programmers may not have the depth
knowledge of the system to be developed. So, it is desirable for the programmers
to understand properly the functionality of the system and they must listen to the
customers[ CITATION gee19 \l 1033 ].
 Designing: Without a proper design, a system implementation becomes too
complex and very difficult to understand the solution, thus it makes maintenance
expensive. A good design results elimination of complex dependencies within a
system. So, effective use of suitable design is emphasized[ CITATION gee19 \l
1033 ].
 Feedback: One of the most important aspects of the XP model is to gain feedback
to understand the exact customer needs. Frequent contact with the customer makes
the development effective[ CITATION gee19 \l 1033 ].

19
 Simplicity: The main principle of the XP model is to develop a simple system that
will work efficiently in present time, rather than trying to build something that
would take time and it may never be used. It focuses on some specific features
that are immediately needed, rather than engaging time and effort on speculations
of future requirements[ CITATION gee19 \l 1033 ].

Advantages of Extreme programming

 One of the major advantages of Extreme Programming is that it reduces the
risks related to programming or related to project failure. At the end XP
ensures that the client gets exactly what he wants.
 Simplicity is one more advantage of Extreme Programming projects. The
developers who prefer to use this methodology create extremely simple code
that can be improved at any moment.
 The basic advantage of XP is that the whole process is visible and
accountable. The developers make concrete commitments about what they
will accomplish, show concrete progress.
 Constant feedback; demonstrate the software early and often, listen carefully
and make any changes needed. Sprints help the team to move in the right
direction.
 This approach creates working software faster. Regular testing at the
development stage ensures detection of all bugs, and the use of customer
approved validation tests to determine the successful completion of a coding
block ensures implementation of only what the customer wants and nothing
more[ CITATION EKA17 \l 1033 ].
 Extreme Programming helps increase employee satisfaction and retention.
Extreme Programming is a value-driven approach that sets fixed work time,
with little scope for overtime. The breakdown of project scope into
subcomponents and the constant customer feedback prevents accumulation of
much work to be completed before a tight deadline[ CITATION EKA17 \l
1033 ].
Disadvantages of Extreme Programming
 Some specialists say that Extreme Programming is focused on the code rather
than on design. That may be a problem because good design is extremely

20
 important for software applications. It helps sell them in the software market.
Additionally, in XP projects the defect documentation is not always good.
 Lack of defect documentation may lead to the occurrence of similar bugs in
the future.
 One more disadvantage of XP is that this methodology does not measure code
quality assurance. It may cause defects in the initial code.
 XP is not the best option if programmers are separated geographically.

Why Extreme programming for E-Smart Kindergarten Management System?

Due to this application environment, researcher would like to recommend the XP
method of developing software development life cycle for smart kid Kindergarten
system.
There are some roles that are active on XP methodology
 Customer
 The developer
 The tracker
 The coach
Client for kindergarten framework is their position who gives the undertaking and
chooses to system change and necessities.
Researchers understand the prerequisites given by Smart Kid kindergarten system.
The entire advancement process is dealt with by engineers. What's more, at times the
entire group falls under engineers alongside developers who compose the code for
web utilization of brilliant child kindergarten framework.
The tracker is one of the engineers who track the pertinent measurements that the
group feels to follow the vital activities. The key measurements that group will follow
are speed of advancement, purposes behind changes of speed, measure of extra time
worked, breezing through and coming up short tests.
The values provided by Extreme programming
 Simplicity: - The steps occupied by the research team are simple due to
fragmented tasks. The involvement of researcher follows the simple steps to
the goal and mitigates failure as they happen. The development team will
create something they are proud of and maintain its long term for reasonable
costs.

21
 Communication: - Everyone is part of researcher and team members
communicate daily. The team works together in the whole thing from
prerequisite of code. The team will provide the best explanation that can be
cracked by collaborating effectively.
 Feedback: - The team will take every iteration commitment seriously by
delivering working web application. The team demonstrates the web app early
and often then listens carefully and makes any changes needed to make. The
team will talk about the project and adopt the process to it.
 Respect: - Everyone on the team gives and takes respect from each other.
Everyone on the team provides value even if it’s simply an enthusiasm.
Developers of the team members respect the expertise of customers. Even the
management respects the team’s right to accept responsibility and receive
authority to the own work.
 Courage: - The team will tell the truth about the projects and estimates. The
team does not document excuses the failure because the team plans to succeed.
The team does not fear anything because no one works alone in the team. The
team adopts the changes whenever necessary.

22
Waterfall Methodology:
Waterfall is a information development methodology is a traditional method
following principle of continuous workflow for developing a system from its initial
stage to the end. The methodology is simple and follows phases to plan, design, and
implement the system ideas before testing, launching and maintaining the system.

Figure 8: Waterfall Method

Guided by the project manager, the methodology requires planning of departments

and ideas such that the phases can be followed timely and complete resources can be
assembled, utilized and synchronized to create the complete system into one. Then the
system is tested and deployed.
Waterfall being a traditional method functions in simple with designated goals with
correct information. Due to this, waterfall is still used in the current times to develop
system either in absence or presence of agile methods to create systems.

23
3. System Analysis
System Analysis is a problem solving technique that decomposes a system into
component pieces for the purpose of studying how well those component parts work
and interact to accomplish their purpose. The system analyst is a specialist who
studies the problems and needs of an organization to determine how people, data,
processes and information technology can accomplish the improvement for the
business. Our group of expert and qualified system analyst has developed the proper
planning regarding various structures of the proposed E-Smart Kid: Kindergarten
Management System. According to the needs and requirement of the Kindergarten
Management System, the system analysis is carried out through different process. The
proper analysis of the proposed system is done by our team of experts and the
identified all the aspects of the project such as cost, time and required technology
needed to complete the system. The system analysis is an important phase in
developing a system where different requirements are gathered using different
techniques and they are as follows:
 Interview
 Document View
 Observation
 Survey and Questionnaire
 Sampling Resource
 Research
3.1 Requirement Elicitation
Requirement elicitation is a process or the practice to find out the requirement for an
intended system by communicating with client, end users and other stake holders. In
other words requirement elicitation is also called requirement gathering. The
requirement elicitation can be done by various methods such as interviews, surveys,
questionnaire, observation, brainstorming, prototyping and so on. The team of expert
analyst will analyze the operation for which the new system is required through these
methods. One of the easiest ways to analyze the system is observation. Here our team
of expert visited the client’s workplace and observed the actual working of the
existing system. They also observed the workflow at the client’s end and how the

24
execution problems are dealt. After the observation of the existing system the team
draws some conclusion which will be helpful for the new system. Hence all the data
are analyzed and requirements of the proposed system are collected. For the proper
analysis of the system, requirement elicitation is further divided and they are as
follows:
 Exploratory Analysis
 Model Fitting
 Model Building
 Sensitivity Analysis
 Reporting

3.2 Data Analysis

Data analysis is the process in which the raw data is transformed and cleaned to
discover useful information. In general the raw data is first collected and stored which
is then cleaned to remove invalid data or redundant data. After the cleaning of the
collected data, the data will be further analyzed for the required system specification.
Some of the important methods of data analysis are as follows:

 Data Cleaning
 Data Association
 Data Visualization
 Data Compilation
 Conclusion

The system that we created is web based system with database for collecting and
storing the data. As a web based system with database the data compilation is
necessary to merge data from different sources and for the irrelevant information.
After the compilation of data, separate reports are created for analyzed data and for
compiled data that makes report more flexible. For further analysis, our team of
expert analyst performed and compared other system for the improvement of the
proposed system. Also the final report of the data analysis is prepared of the system.

25
3.3 Data Presentation:
The data should be presented in such a way that the facts and figures are clearly
understood and are capable of being analyzed. The analyzed and compiled data which
are collected from the users are presented in the form of textual or tabular form. The
presented data is then presented in a report for the further design of the proposed
system. The designing team analyzes the data and the required design is made for the
completion of the system. The designing team further converts the presented data in to
useful diagrams. After the data presentation, scheduling is made for the development
of the project. All the requirements such as time, cost is also further presented for the
development and completion of the proposed system. Data is presented through
various methods such as tables, figures, bar graphs, line graphs etc to represent

Figure 9: Data Presentation Methods

26
4. System Design
System designing can be described as process of sketching and interpreting the
construction, interface structure, system modeling, functional designs and
collaborative interface function of user with the system developed to meet the
requirements of the system to be developed. It is the use of systematic approach to
create the architecture, logic and physical design by considering all the variables and
elements that are to be satisfied such as hardware, software, security, efficient use and
data communication. System designing is an important part of creating a system. It
can simply be referred to sketching and implementing the complete modeling of a
system. The concept of system designing was introduced near the events of World
War II in 1990s, after the requirement to solve complexities in data communication
and security. Building such system designs aided in creating a standard in projects
such that people could work with the standardized hardware and software to build
conventional system designs. The process had fulfilled the criteria of building the
input-output flow, storage, interface, architecture and the logic to satisfy the
requirement of a fully functional system with better data handling and user-system
interaction. The following points were taken into consideration to build the basic
system design:
a. Physical Design:
Physical Design refers to designing the concept of Input-Process-Storage-
Output within the system in addition to concerning its data backup and
recovery. Physical design is the way to create the models for the flow of how
the data is taken in and how it is displayed to the user. Designing the physical
portion requires building three factors including of:
i. Interface of the system
ii. Data
iii. Process
It is very crucial to sketching the physical design of the system since the data
input and handling relies upon how good the physical design is built. It is also
important that all the entities (internal and external) have to be included in the
design to show the implication of input to process the result to be displayed to
the user.

27
b. Logical Design:
Logical design refers to the development of the I/O design and data logics. It
simply reflects the flow of data within the system by using simple logics and
the concept of arranging those data in logical algorithm chains. A logical
design is always drawn before the physical design is set for the system. It is
often sketched by drawing a design over a generic concept and models as well
as graphical modeling of the actual system.
c. Architectural Design:
Architectural design refers to sketching the structural and behavioral
components of the system. It is the representation of components of the
program and the data required to build a fully functional system. Architectural
designing does not deal with the operational function such as logical and
physical design but represents how the program is modeled to serve system.
Architectural diagram is drawn by representing the models of the contents and
context internal entities and system acts with external entities.
The current project has to involve development of several physical, logical and
architectural designs in order to create fulfillment of complete entities and
attributes. The E-Smart Kindergarten is a web-based system collaborated with
database. Our team over Professional IT Pvt. Ltd. has discussed and has used
the following tools and designs to create the model of the system:
 UML:
- Use Case
- DFD
- Class Diagram
- Activity Diagram
- Context diagrams
 HCI (Human Computer Interface):

28
4.1 USE CASE DIAGRAM (Behavioral UML) :

Figure 10 Activity Diagram for E-Smart Kid: Kindergarten Management System

The above class diagram is a design created for the Smart Kindergarten System that
clarifies the tasks of each entities and users in the program created for the system. As
shown above and required by the system, the user: administrator is able to access the
function of managing the students’ information and the schedules in the kindergarten.
As for the user: Academic staffs, they can record and manage students’ attendance but
will have the priorities limited to just viewing the assigned schedules and student’s
information. Lastly the academic staffs will also be able to create individual results
depending upon the information of the student’s intake record.

29
4.2 CLASS DIAGRAM (Structural UML):

Smart-Kid KinderGarten Management System

Figure 11: Class Diagram for E-Smart Kid

The above diagram shows the class diagram used for programming the E-Smart Kid:
Kindergarten System. The above class diagram shows how different classes are
created for developing ideas into codes for structures of the program initialized from
one class to another with relation to each other.

30
4.3 DATA FLOW DIAGRAM (Data flow UML):

Figure 12: DFD for E-Smart Kid

The above diagram shows the data flow of records and information towards different
towards the web application server. Every data is sent into the server backed-up and
later accessed by the users in order to work with the data.

31
4.4 Physical designs: Frames
a. Home Page:

Figure 13: Home Page Design

The above shown figure represents the design of E-Smart Kid: Kindergarten
management application on its home. After surfing the internet into www.smart-
kindergarten.com, the home page opens up and displays the following page. The
home page consists of basics functions in a web page such as slides and images, tabs
for switching into other features, maps for location, help button for consulting the
administration and lots of information about the organization, The site can be used by
all general public and academically involved people alike.

32
b. Login Page:
The figure below shows the login page of the E-Smart Kid Kindergarten
Management System. The page is displayed after the user taps in into the login
button on home page.

Figure 14: Login Page The

login page asks for login from the user the type it is switched into:
Administrator or the academic staff. Then username and password is required
to log-in into next page.

33
c. Administrator Section:

Figure 15: Admin Page Design

The above page shows the page created for administrative function. The
functions include managing student info, schedules, staff accounts as well as
settings on administrative page.

34
 d. Academic Staff Section:

Figure 16: Academic Staff Page design

The above design shows the design of academic staff page. The functions of the page
include managing attendance, academic profile of students for registration, viewing
schedules assigned by the administrator, viewing students’ progress and info and
developing results of the students.

35
5. Implementation and Deployment
The implementation and deployment is one of the important phases of any system
development. After the designing of the system the system will be handed over to the
programmers. The design will be converted into programming language. Then the
programmer will make a complete system based on logical structure of the system.
The testing of the program will be done until the requirement meets the design phase.
After the designing the system, the rest of system is developed in three different
phases and they are as follows:

 Construction
 Testing
 Deployment

5.1 Construction
The construction phase is used after the The web-application is the firstly
implemented via the construction process. The web based application is developed by
using HTML as its base then collaborated with CSS, JavaScript PHP on its framework
Laravel by using Adobe Dreamweaver. The major languages and tools used for the
construction of the web application are listed below:

Tools Functions
Adobe Adobe Dream-weaver CC is web development tool developed by
DreamWeaver Adobe Inc.
Dreamweaver makes live coding and code editing easier with actual
time with both graphical and text building using different languages.
Our team has built the web page and the application using
Dreamweaver tool to develop it through HTML,CSS, PHP and JS.
HTML HTML stands for Hypertext Markup Language, a standard language
used to creating web pages and web application. Like other markup
languages, it is used to generate a basic webpage by manipulating the
series of texts and documents in order to create base of a web page
with lots of information, graphics and user interface on HTTP for
collective system designs.
The team created the basic webpage for the system by using HTML

36
 codes to build the basic functions of the web page.
CSS CSS stands for Cascading Style Sheets used for expressing the style
and format of HTML. CSS is used for creating the layout for the
presentation and the contents with fonts and colors to improvise in
nearness and plasticity of the markup languages in the web
document. In the development of the page, we have used CSS with
HTML to create the design of the web page for functional UI
planning.
PHP: Laravel PHP stands for Hypertext Pre-Processor or Personal Home Page. It is
a widely used language coded in command lines then embedded to a
markup language, generally used in HTML for executable
applications within the web page. PHP can be used as a standalone
language to create applications and controlling mechanical robots.
Laravel is an open source PHP framework used for developing web
applications. The use of bundle packaging for application addition
with its robustness and dedication in retrieving utilities and data from
databases, application formation is efficient and elementary in the
language; the team chose Laravel web application development for
extensible, steady development and logical applications.
React: JavaScript or JS is a prototype-oriented language with efficient
JavaScript argument passing widely used to fabricate interaction to exhibit static
information in web browsers. JavaScript is one of the core languages
for building standard web technology alongside HTML and CSS for
creating interaction in web pages to assist in applications with the use
of APIs.
The team proposed and implemented the use of React JS in the
system to build the interface of the system, to store input variables,
operations and response in pages since, it can be used to exhibit the
application in mobile responsive feature.
Mongo DB Mongo Database System is the one of the widely used transverse
application database system in the current times. It is an open source
database providing users with tall performance and compatibility on
queries, indexing and supports even non-schema databases in
addition to high availability. Mongo DB system plays the sole role in
creating database system in the project due to its dynamic schema

37
 and scalability with supporting JSON library used by React JS.
Objects, Source code of complete objects and procedures are included in the
procedures system after the use of the compiler to process the application to
and source exhibit accomplished application system.
codes
User Manual User Manual is one of the most essential perquisites to run any
application. The team has included a help and user manual feature to
aid users to run the application with descriptive procedure by
procedure tutorials. The User manual includes graphical and
characterized lessons for the user to access the system describing all
operational modes and functions in the system.
Copyright Copyright consists of license file that protects the use and right of the
clients and us developers.

Figure 17: Tools for E-Smart-Kid

38
5.2 Testing
After the successful construction of the system, testing will be done to find any errors
and bugs in the system. Basically the testing is done to find any bugs or errors in the
system. Testing helps in the improvement of the system since it checks all the errors
and faults in the built system. The testing is done to check the quality of system where
its flexibility, function, security and behavior are checked thoroughly.
Testing is done lastly after to make sure the applications can operate successfully over
multiple platforms. Testing is done through functional and non-functional
methodology to complete the release of a fully developed system. Therefore the
system will be tested by our team of experts and analyst for final time before handing
over the system to our clients. We have chosen our system to go through the
functional and non-functional testing methodologies for final release.
5.2.1 Functional Testing
The functional testing is used for verifying each functions of the software if they can
be run in a specified consoles and systems. These testing include black box testing for
internal structure and design. Functional testing requirement the fulfillment of the
following methods:
 Unit Testing:
The unit testing is done to determine if there is any issue by the developer
himself. The main aim of unit testing is to identify, analyze and fix the defects
in the system. This testing is conducted to check the small errors that is done
by the developer and while testing if there are no faults then the test continues
and other test are conducted.
 Functional Testing:
Functional testing is the testing of all the functional units of the system that
covers all scenarios in the web page, non-responsiveness of web page,
boundary cases and so on. Functions or features of the system are tested that
ensures the requirements are satisfied by the system. The functional testing is
usually done to check the database, user interface, security and the
functionality of the application software.
 System testing:
The system technique is a black box testing technique that is done to check
whether the system performs according to the system requirements. The

39
 system testing is done to check the flexibility of the proposed system i.e. E-
Smart Kid: Kindergarten Management System. The functional testing is
carried out by our team of expert to measure the quality of the system
proposed.
5.2.2 Non-Functional Testing
Non-functional testing is used to check non-functional features of the systems that
include performance, usability, reliability etc. of the application. The non-functional
testing includes all the parameters that are not addressed by the functional testing
criteria. The non-functional testing methods are done through the following methods:
 Performance testing
 Security testing
 Usability testing
 Compatibility testing
These procedural testing is done for checking the quality of software and efficiency
for adoption to users to build strong framework that implements both functional and
non-functional testing methodologies.

40
5.3 System Deployment
The system deployment refers to the physical transfer of the technology to the
organization’s operating system. In other words, system deployment refers to the
system that is ready to be delivered to client or customers. Before the system
deployment, the entire system is tested and checks whether the system is fully
functional. The system deployment test is done which are called pre-deployment test
and post deployment test The pre –development test is done on the production site
where the developers test for the final time before system deployment. The post
deployment test is also called on-site test which are done to spot new problems in the
system. There are four changeover deployment methods for the system deployment
which are as follows:
 Parallel Changeover
In parallel operation the new system runs simultaneously with old system for a
given period of time which is most popular operation having low risk. This
changeover method is time consuming where problems are easily identified by
comparing input and output of the system. If something goes wrong in the
changeover, the entire system can be reverted back to its original state. A
primary disadvantage of this system is higher cost since we have to run two
systems simultaneously.
 Phased Changeover
In this system some amount of new system is applied over the old system in
order to check the errors in the system. In other words, this changeover
method is also considered as a compromise between parallel and direct
changeovers. In this changeover the new system is implemented one stage at a
time. The changeover cost is low but it takes a long time to complete because
phases need to be implemented separately. If there is no error in the system
other parts are deployed to complete a new system.
 Pilot Changeover
Pilot Changeover is the combination of parallel and direct changeover
methods. It is the kind of changeover technique where the new system is
operated by small group of the company, which is called the pilot site. The old
system is on the use by the greater group and the new system is replaced
directly like parallel changeover but after data analysis on finals extraction.

41
 Pilot changeover is rather costly since the old and the new system are on use
dually by the organization. Pilot changeover despite being expensive is rather
fruitful since the decisions are based on analyzed results and bear not much of
risks and threats.
 Direct Changeover
Direct Changeover technique is the term used when the organization directly
replaces its old system with the new system without any phased tests or
timeframe for checking the functionality of the system. Direct Changeover
technique is the least used technique out of all changeover practices due to
unreliable results that may either be positive or even negative outcomes.
Direct changeover saves a lot of money, time and manpower since it requires
no testing phase. The practice of direct changeover is used by a company
when they are low on resources and are ready to take risks. The most
disadvantageous point of this method comes in time of reverting back, since
reversal is impossible and cause a lot of loss to revert to buy the old system.

Deployment for E-Smart Kid system:

For our system deployment we have chosen the direct changeover method for
development since there is no presence of current system in use thus, the
system is deployed directly into the organization with required trainings. The
system is directly to be deployed and all of the manual systems are to be
directly replaced.

42
6. Conclusion
E-Smart Kid: Kindergarten Management System is a computerized records
system. This management system has been very adventitious over manual system.
Before this system the kindergarten used to work in a manual system that was very
time consuming as all the work was done using spreadsheet. Manual system was time
consuming and ineffective with high consumption of resources. .
The main purpose of the system is to reduce the burden for staffs, and to improve
overall student’s record. This system has helped a lot in terms of data storage and data
retrieval where all the data's are saved in a database.
As a conclusion, the proposed system will bring many benefits to administrative
staffs, academic staff’s and all the students of the kindergarten. The work load will be
reducing and planning can be schedule more effectively. The E-Smart Kid:
Kindergarten Management System is developed using different agile methodology.
Hence this system can be deployed for the smooth running of the organization.

43
Reference
(n.d.). Retrieved from https://www.testingbrain.com/pdf-tutorials/scrum-
methodology-tutorial.html

agileallince. (2019, 05 06). glossary/xp/. Retrieved from agileallince.com:

https://www.agilealliance.org/glossary/xp/#q=~(infinite~false~filters~(postTy
pe~(~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'
aa_research_paper~'aa_video)~tags~(~'xp))~searchTerm~'~sort~false~sortDir
ection~'asc~page~1)

Alkazam. (n.d.). extremeprogramming. Retrieved 2018, from

http://www.extremeprogramming.org/

Amir. (n.d.). extremeprogramming.org. Retrieved 2018, from

http://www.extremeprogramming.org/when.html

Bates, C. (2003). Web Programming Building internet Applications (2nd ed.). Delhi:
WILEY-dreamtech india pvt. Ltd.

C.Layton, M. (2017). Dummies. Retrieved September 24, 2018, from

http://www.dummies.com/careers/project-management/the-12-agile-
principles/

Conway, K. (2005). Software Project Management (2nd ed.). Delhi: polyKam

Printers.

geeksforgeeks. (2019, 05 06). software-engineering-extreme-programming-xp/.

Retrieved from GeeksforGeeks: https://www.geeksforgeeks.org/software-
engineering-extreme-programming-xp/

Grag, P. (2017). openxcell. Retrieved September 24, 2018, from

https://www.openxcell.com/agile-methodology-important-start

NDHS. (2006). Nepal Demographic Health Survey. Nepal Demographic Health

Survey.

NOVOSELTSEVA, E. (2017, 03 02). tech-blog-barcelona/extreme-programming-

tips-advantages/. Retrieved from apiumhub: https://apiumhub.com/tech-blog-
barcelona/extreme-programming-tips-advantages/

Robertson, T. (Nil). Chron. Retrieved 2018, from

http://smallbusiness.chron.com/changeover-techniques-34890.html

Russo, N. F. (2002). Information Systems Developments Methods In Action.

McGraw Hill.

44
santi. (Nil). dlsi. Retrieved 2018, from
https://www.dlsi.ua.es/~santi/papers/WebSA_ICWE2004

SEO, L. (2017, 10 23). A beginners guide to understanding agile method. Retrieved

2018, from Linchpin SEO: https://linchpinseo.com/the-agile-method/

Wikipedia. (2011). Agile Software Development: Extreme Programming, Wabi-Sabi,

Dynamic Systems Development Method, Feature Driven Development,
Scrum, Devops. Books LLC, Wiki Series.

45
Appendix:
Gantt charts:

Figure 18: Group Gantt Chart

46
 Figure 19: Individual Gantt Chart: Niraj Thapa

Figure 20: Individual Gantt Chart: Prashil Khadka

47
Figure 21: Individual Gantt Chart: Sonam Rinzing Tamang

48
 Group Component (70%)
Group Members:

Name: Niraj Thapa Name: Prashil Khadka Name: Sonam Rinzing Tamang

TP No: NP000199 TP No: NP000202 TP No:NP000207

CSSF Very Poor Poor Adequate Good Excellent

1. Project Planning
1.1 Introduction No evidence in Done but missing Brief introduction. Clear, complete yet Clear, complete
(5%) documentation critical information Some missing / very basic and detailed
or softcopy. such as business vague description introduction. introduction.
Too little process and of business process All business process Detailed and
evidence was overview of and overview of and overview of precise description
found. proposed system. proposed system. proposed system of business process
Mostly irrelevant Some irrelevant made but briefly and overview of
information. information. discussed/identified. proposed system.
No irrelevant All relevant
information. information.
Marks 0 1 2 3 4 5
1.2 Aim, Objectives No evidence in Done but missing Brief introduction. Clear, complete yet Clear, complete
and Scopes (5%) documentation critical information Some missing / very basic and detailed
or softcopy; or such as aim, vague description introduction. All introduction.
very briefly objectives and of aim, objectives aim, objectives and Detailed and
done. scopes. Mostly and scopes. Some scopes made but precise description
irrelevant irrelevant briefly of aim, objectives
information information. discussed/identified. and scopes. All
No irrelevant relevant
information. information
Marks 0 1 2 3 4 5
2. Agile Principles
and IS
Methodology
2.1 Agile Principles No evidence in Done but only State at least 5 State at least 10 Include all agile
(10%) documentation stated 1 or 3 agile agile principles agile principles with principles with a
or softcopy; or principles but there with a vague a clear connection very clear
very briefly is no connection connection between the connection
done but there between the between the principles and between the
is no principles and principles and project. Brief principles and
connection project. Mostly project but only explanation is given project. Detail
between the irrelevant some of the for each point with explanation is
agile principles information. information is mostly relevant given for each
and the project. relevant. information. point with relevant
information.
Marks 0 1 2 3 4 5 6 7 8 9 10
2.2 IS Methodology No evidence in Done but only state Brief introduction Clear introduction Clear and detail
(10%) documentation 1 methodology that on 2 on 3 methodologies introduction on 4
or softcopy; or is related to agile methodologies that that are related to methodologies that
done briefly methodology. No are related to agile the agile are related to the
with comparison is methodology. methodology. agile methodology.
methodology made with another Comparison is Comparison is made Comparison is
that is not methodology. No made between the between the made between the
related to the summary on the methodologies. methodologies. methodologies.
agile topic is given. Summary is made Summary is made Summary is made
methodology. on the topic but on the topic but with on the topic but
with a brief detail explanation with detail
explanation on the on the advantages of explanation on the
advantages of each each methodology. advantages of each
methodology. methodology.
There is brief
49
 explanation that
relates the
advantages to the
project.
Marks 0 1 2 3 4 5 6 7 8 9 10
3. System Analysis No evidence in Done but missing Brief introduction Clear, complete and Clear, complete
(10%) documentation critical information on the chosen yet very basic and details
or softcopy; or such as description analysis introduction on the explanation on the
very briefly of the chosen techniques. There chosen analysis chosen analysis
done. analysis. No is a vague techniques. Clear techniques. Clear
evidence on the connection connection between and details
analysis techniques between the the analysis connection
that can be related analysis techniques techniques with the between the
to the project. with the project. project. Clear analysis techniques
No justification Justification is not justification with with the project.
made on the choses clear but with mostly relevant Detail justification
analysis. Mostly some relevant information. is given with
irrelevant information related relevant
information to it. information.
Marks 0 1 2 3 4 5 6 7 8 9 10
4. System Design No evidence in Done with just one Done with two Done with three Done with four
(10%) documentation system design is system design is system design is system design is
or softcopy; or chosen such as chosen such as chosen such as chosen such as
very briefly system system system architecture, system
done. architecture, architecture, software/hardware architecture,
software/hardware software/hardware architecture, logical software/hardware
architecture, architecture, design or physical architecture,
logical design or logical design or design. Diagrams logical design or
physical design. physical design. available with minor physical design.
Missing diagram Diagrams are errors or illogical Diagrams are
and / or available with components. available with no
components. many errors related Diagram closely or minor errors.
Diagram produced to naming related with the Diagrams closely
is not related to conventions, findings of the related with the
findings of the violation of investigation phase. findings of the
investigation diagramming rules. investigation
phase. Many major Some illogical phase.
errors in diagram components within
related to naming the diagram.
conventions, Diagram related to
violation of the findings in the
diagramming rules. investigation
Totally illogical phase.
diagram produced.
Marks 0 1 2 3 4 5 6 7 8 9 10
5. Implementation
and deployment.
5.1 Construction No evidence in Done with just a Brief introduction Clear, complete yet Clear, complete
documentation list of the chosen on each of the very basic and detailed
or softcopy; or software and chosen software or introduction of the introduction of the
very briefly hardware. No hardware. chosen software and chosen software
done. explanation or Explanation and hardware. Clear and hardware
justification is justifications are explanation and including with
provided. vague and mostly justification with related pictures
the information is mostly relevant Clear and detailed
irrelevant. information. explanation and
justification is
given with relevant
information.
Marks 0 1 2 3 4 5
5.2 Testing No evidence in Done but missing Brief introduction Clear, complete yet Clear, complete
documentation critical information on the chosen very basic and detailed
or softcopy; or of the chosen types types of testing. introduction on the introduction on the

50
 very briefly of testing. No on Some missing / chosen types of chosen types of
done. explanation and vague explanation testing. testing.
justification and justification Clear explanation Detailed and
indicates the between the and justification precise explanation
relation between chosen types of between the chosen and justification
the chosen types of testing and the types of testing and between the
testing and the project. the project. chosen types of
project. Mostly Some irrelevant Mostly relevant testing and the
irrelevant information. information project with
information. relevant
information.
Marks 0 1 2 3 4 5
5.3 Deployment. No evidence in Done but missing Brief introduction Clear, complete yet Clear, complete
documentation critical information on system change very basic and detailed
or softcopy; or system change over strategy. introduction on introduction on
very briefly over strategy. No Some missing / system change over system change
done. on explanation and vague explanation strategy. Clear over strategy.
justification is and justification is explanation and Detailed
given Mostly given. justification with explanation and
irrelevant Some irrelevant ‘how to deploy’ the justification with
information. information. system in the ‘how to deploy’
organization. the system in the
Mostly relevant organization is
information given with relevant
information.
Marks 0 1 2 3 4 5

Comments:
_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

51
Individual Component (30%)
Name: Niraj Thapa
TP No: NP000199
CSSF Very Poor Poor Adequate Good Excellent
6. Selected No evidence in Done but missing Brief introduction Clear but basic Clear and detail
Methodology documentation or critical information on methodology introduction on introduction on
(15%) softcopy. about the and it t is related methodology and the chosen
Too little evidence methodology. to agile it is related to the methodology and
was found. Chosen methodology. agile it is related to the
methodology is not Vague explanation methodology. agile
related to agile. and justification is Clear explanation methodology.
Poor explanation given. Little and justification Clear and detail,
and justification is connection is given and it is explanation and
given. Irrelevant between the related to the justification is
information. chosen diagram. Clear given and it is
methodology and connection related to the
project. Mostly between the diagram. Clear
relevant chosen connection
information is methodology and between the
given. project. Relevant chosen
information is methodology and
given. project. Relevant
information is
given.
Marks 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
7. Project No evidence in Done but the listed Tasks are listed Tasks are listed Tasks are listed
Scheduling documentation or tasks are no nicely and nicely and nicely and
(5 %) softcopy. organized and organized. All the organized. All the organized. All the
Too little evidence some of the task sub-tasks are sub-tasks are sub-tasks are
was found. are irrelevant to relevant to the relevant to the relevant to the
the project. No project. Vague project. Clear project. Clear
connection connection connection connection
between the chart between the chart between the chart between the chart
and the chosen and the chosen and the chosen and the chosen
methodology. methodology methodology methodology
Missing important Missing important Minor charting Complete chart
component of the component of the mistakes. with no mistakes
chart. chart. is given together
with the summary
on project
duration.
Marks 0 1 2 3 4 5
8. Presentation Most questions not Not able to answer Able to answer Able to answer Excellent
(10%) answered. some questions. questions. Some questions. No presentation skill
Reading from Reading from reading from reading from with clear and
text/slide most of text/slide. Some text/slide. text/slide. Smooth complete slides.
the time. Seems flow of Acceptable flow flow of Good
unstructured and explanation of explanation and explanation and understanding of
unprepared with available and show some shows knowledge the system
very little seems to knowledge of the of project. specification and
knowledge of the understand what project clear
project. the project is all undertaken. demonstration of
about. the design.
Answer to answer
questions.
Marks 0 1 2 3 4 5 6 7 8 9 10

Total Marks (Group Component): _________/70%

Total Marks (Individual Component):_________/30%

52
Total Assignment Marks: __________/100%

Comments:
_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

53
Individual Component (30%)
Name: Sonam Rinzing Tamang
TP No: NP000207
CSSF Very Poor Poor Adequate Good Excellent
9. Selected No evidence in Done but missing Brief introduction Clear but basic Clear and detail
Methodology documentation or critical information on methodology introduction on introduction on
(15%) softcopy. about the and it t is related methodology and the chosen
Too little evidence methodology. to agile it is related to the methodology and
was found. Chosen methodology. agile it is related to the
methodology is not Vague explanation methodology. agile
related to agile. and justification is Clear explanation methodology.
Poor explanation given. Little and justification Clear and detail,
and justification is connection is given and it is explanation and
given. Irrelevant between the related to the justification is
information. chosen diagram. Clear given and it is
methodology and connection related to the
project. Mostly between the diagram. Clear
relevant chosen connection
information is methodology and between the
given. project. Relevant chosen
information is methodology and
given. project. Relevant
information is
given.
Marks 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
10. Project No evidence in Done but the listed Tasks are listed Tasks are listed Tasks are listed
Scheduling documentation or tasks are no nicely and nicely and nicely and
(5 %) softcopy. organized and organized. All the organized. All the organized. All the
Too little evidence some of the task sub-tasks are sub-tasks are sub-tasks are
was found. are irrelevant to relevant to the relevant to the relevant to the
the project. No project. Vague project. Clear project. Clear
connection connection connection connection
between the chart between the chart between the chart between the chart
and the chosen and the chosen and the chosen and the chosen
methodology. methodology methodology methodology
Missing important Missing important Minor charting Complete chart
component of the component of the mistakes. with no mistakes
chart. chart. is given together
with the summary
on project
duration.
Marks 0 1 2 3 4 5
11. Presentation Most questions not Not able to answer Able to answer Able to answer Excellent
(10%) answered. some questions. questions. Some questions. No presentation skill
Reading from Reading from reading from reading from with clear and
text/slide most of text/slide. Some text/slide. text/slide. Smooth complete slides.
the time. Seems flow of Acceptable flow flow of Good
unstructured and explanation of explanation and explanation and understanding of
unprepared with available and show some shows knowledge the system
very little seems to knowledge of the of project. specification and
knowledge of the understand what project clear
project. the project is all undertaken. demonstration of
about. the design.
Answer to answer
questions.
Marks 0 1 2 3 4 5 6 7 8 9 10

Total Marks (Group Component): _________/70%

Total Marks (Individual Component):_________/30%

54
Total Assignment Marks: __________/100%

Comments:
_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

55
Individual Component (30%)
Name: Prashil Khadka
TP No: NP000202
CSSF Very Poor Poor Adequate Good Excellent
12. Selected No evidence in Done but missing Brief introduction Clear but basic Clear and detail
Methodology documentation or critical information on methodology introduction on introduction on
(15%) softcopy. about the and it t is related methodology and the chosen
Too little evidence methodology. to agile it is related to the methodology and
was found. Chosen methodology. agile it is related to the
methodology is not Vague explanation methodology. agile
related to agile. and justification is Clear explanation methodology.
Poor explanation given. Little and justification Clear and detail,
and justification is connection is given and it is explanation and
given. Irrelevant between the related to the justification is
information. chosen diagram. Clear given and it is
methodology and connection related to the
project. Mostly between the diagram. Clear
relevant chosen connection
information is methodology and between the
given. project. Relevant chosen
information is methodology and
given. project. Relevant
information is
given.
Marks 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
13. Project No evidence in Done but the listed Tasks are listed Tasks are listed Tasks are listed
Scheduling documentation or tasks are no nicely and nicely and nicely and
(5 %) softcopy. organized and organized. All the organized. All the organized. All the
Too little evidence some of the task sub-tasks are sub-tasks are sub-tasks are
was found. are irrelevant to relevant to the relevant to the relevant to the
the project. No project. Vague project. Clear project. Clear
connection connection connection connection
between the chart between the chart between the chart between the chart
and the chosen and the chosen and the chosen and the chosen
methodology. methodology methodology methodology
Missing important Missing important Minor charting Complete chart
component of the component of the mistakes. with no mistakes
chart. chart. is given together
with the summary
on project
duration.
Marks 0 1 2 3 4 5
14. Presentation Most questions not Not able to answer Able to answer Able to answer Excellent
(10%) answered. some questions. questions. Some questions. No presentation skill
Reading from Reading from reading from reading from with clear and
text/slide most of text/slide. Some text/slide. text/slide. Smooth complete slides.
the time. Seems flow of Acceptable flow flow of Good
unstructured and explanation of explanation and explanation and understanding of
unprepared with available and show some shows knowledge the system
very little seems to knowledge of the of project. specification and
knowledge of the understand what project clear
project. the project is all undertaken. demonstration of
about. the design.
Answer to answer
questions.
Marks 0 1 2 3 4 5 6 7 8 9 10

Total Marks (Group Component): _________/70%

Total Marks (Individual Component):_________/30%

56
Total Assignment Marks: __________/100%

Comments:
_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

_______________________________________________________________________________________
________

57
Work Load Matrix:
S.N. Individual members Work load percentage

NP000202 Prashil Khadka 33.33%

NP000199 Niroj Thapa 33.33%

NP000202 Sonam Rinzing Tamang 33.33%

58