Você está na página 1de 56

-

Assignment Brief
BTEC Level 4-5 HNC/HND Diploma (QCF)

To be filled by the Student


Name of the Student : Hansani Chathurani

Edexcel No : Registration No: KLT/A-001963 Batch No:003

Unit Assessment Information

Qualification : Higher National Diploma in Computing and Systems Development

Unit Code & Title : K/601/1281 – Unit 09 –SYSTEMS ANALYSIS AND DESIGN (SAD)

Assessment Title & No’s : Stafford University - (SAD – 16 – 001)

Learning outcomes and grading opportunities:


LO 01: Understand different systems life cycles
Learning Outcomes LO1.1 LO1.2

LO 02: Understand the importance of a feasibility study


Learning Outcomes LO2.1 LO2.2

LO 03: Be able to perform a systems investigation


Learning Outcomes LO3.1 LO3.2 LO3.3 LO3.4

Merit and Distinction Descriptor


M1 M2 M3 D1 D2 D3

Date Issued : Date Due :

Date of Submission:

Assessor : Date Assessed:

Internal Verifier (IV): Date of IV:

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 1 of 56


General Guidelines

1. A Cover page or title page – You should always attach a title page to your assignment. Use
previous page as your cover sheet and be sure to fill the details correctly.
2. This entire brief should be attached in first before you start answering.
3. All the assignments should prepare using word processing software.
4. All the assignments should print in A4 sized paper, and make sure to only use one side printing.
5. Allow 1” margin on each side of the paper. But on the left side you will need to leave room for
binging.
6. Ensure that your assignment is stapled or secured together in a binder of some sort and attach
the Softcopy (CD) of your final document, system on last page.

Word Processing Rules


1. Use a font type that will make easy for your examiner to read. The font size should be 12 point,
and should be in the style of Time New Roman.
2. Use 1.5 line word-processing. Left justify all paragraphs.
3. Ensure that all headings are consistent in terms of size and font style.
4. Use footer function on the word processor to insert Your Name, Subject, Assignment No, and
Page Number on each page. This is useful if individual sheets become detached for any reason.
5. Use word processing application spell check and grammar check function to help edit your
assignment.
6. Ensure that your printer’s output is of a good quality and that you have enough ink to print your
entire assignment.

Important Points:
1. Check carefully the hand in date and the instructions given with the assignment. Late
submissions will not be accepted.
2. Ensure that you give yourself enough time to complete the assignment by the due date.
3. Don’t leave things such as printing to the last minute – excuses of this nature will not be
accepted for failure to hand in the work on time.
4. You must take responsibility for managing your own time effectively.
5. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
6. Failure to achieve at least a PASS grade will result in a REFERRAL grade being given.
7. Non-submission of work without valid reasons will lead to an automatic REFERRAL. You will
then be asked to complete an alternative assignment.
8. Take great care that if you use other people’s work or ideas in your assignment, you properly
reference them, using the HARVARD referencing system, in you text and any bibliography,
otherwise you may be guilty of plagiarism.
9. If you are caught plagiarizing you could have your grade reduced to A REFERRAL or at worst you
could be excluded from the course.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 2 of 56


Statement of Originality and Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as
my own without attributing the sources in the correct way. I further understand what it means to copy
another’s work.

1. I know that plagiarism is a punishable offence because it constitutes theft.


2. I understand the plagiarism and copying policy of the Edexcel UK.
3. I know what the consequences will be if I plagiaries or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspects of my program, will be my
own, and where I have made use of another’s work, I will attribute the source in the correct
way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Edexcel UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the attached.

Student’s Signature: …………………………… Date: .………………

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 3 of 56


CASE STUDY

Stafford University

Stafford University is a large institution which provides education to vast number of students. The
University consists three faculties namely Art Faculty, Science Faculty and Management Faculty. Each
faculty is supervised by a dean and it contains 3 departments separately. Art Faculty contains History,
Economic and political science Departments. Science Faculty contains IT, Electronic, Electronic and
Statistical Departments Management Faculty contains Finance, HR and Banking Department. Each
faculty offers different programs and each program can be offered by only one faculty. Each program
has a unique code, title, level and duration. Some programs may have one or more prerequisite courses
and one course can be the prerequisite course of some other courses.

The University employs lecturers to teach students. Each lecturer is assigned an ID which is unique
across the whole university. The lecturer’s name, title and the office room should be recorded for
further reference. A supervisor maybe in charge of several lecturers, but a lecturer, however reports to
only one supervisor. A lecturer can teach many different courses. A course may also have been taught
by many different lecturers.

A batch report is printed for Lecturers indicating which courses they will teach. A course catalog is
printed and distributed to the students.

Currently, the students fill out registration forms that indicate their choice in courses, and return the
completed forms to the Registrar’s office. The typical student load is four courses. The staff of the
Registrar’s office then enters the students’ forms into the computer. Once the students’ curriculum for
the semester has been entered, a batch job is run overnight to assign students to courses. Most of the
time student’s get their first choice; however, in those cases where there is a conflict, the Registrar’s
office talks with each student to get additional choices. Once all students have been successfully
assigned to courses, a hard copy of the students’ curriculum is send to the student’s for their
verification. Most student registrations are processed within a week, but some exceptional cases take
up to two weeks to solve.

Student works on courses are awarded a grade in any course if he/she passes the course. Otherwise the
student has to re-take the failed course. The administrator should keep the record the year and term in
which the course was taken and the grade awarded to the student. Every student has a unique ID and
the Administrator records the student name, birthday and the year he/she enrolled in the course.

According to the higher management decision it is decided to start a new faculty for the students who
wish to enroll with the Software Engineering degree programmer which consists 3 years namely
Diploma, Higher National Diploma and the Degree. With the expansion of faculties the higher
management has decided to go for a feasible Software solution to overcome the limitations of the
existing system and the processes.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 4 of 56


Task 1: LO 1: Understand different systems life cycles

1.1 Evaluate range of different lifecycle models with their suitability and suggest which model best fits
the scenario (LO 1.1) (M1.1) (D 1.1)
1.2 Discuss the importance of following a procedural/staged lifecycle in a systems investigation by
providing the link of each stages and highlight their importance (LO 1.2)

Task 2: LO 2: Understand the importance of a feasibility study

2.1 Prepare a PowerPoint presentation to assess the impact of different feasibility criteria on a systems
investigation including Technical, Economic, Cultural, Legal, Operational and Schedule feasibility by
highlighting their importance (LO 2.2)
2.2 Discuss the components of a feasibility report including structure, intended audience, outcomes
(LO2.1)

Task 3: LO 3: Be able to perform a systems investigation

3.1 Provide a summarized description according to the requirements gathered including scope, inputs,
outputs, processes and alternate solutions (LO3.1)

3.2 Draw a Level 0 (Context) and a Level 1Data Flow Diagrams and draw a ER Diagram
(LO 3.2)
Data Flow Diagram should contain:-
Processes
Data Flows
Entities
Data stores
ER Diagram should contain Cardinality constraints among defined Entities

3.3 Create a documentation including background information, problem statements, data collection
process and summary, recommendations, appendices
(LO 3.3)

3.4 Identify user and systems requirements and evaluate how these requirements have been addressed
through your proposed solution (LO 3.4) (D 3.4)

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 5 of 56


Table of Contents
Task 1 .......................................................................................................................................................... 10
1.1 Evaluate range of different lifecycle models with their suitability and suggest which model best fits
the scenario ............................................................................................................................................. 10
1.2 Discuss the importance of following a procedural/staged lifecycle in a systems investigation by
providing the link of each stage and highlight their importance ............................................................. 18
Task 02 ........................................................................................................................................................ 21
2.1 Prepare a PowerPoint presentation to assess the impact of different feasibility criteria a systems
investigation including Technical, Economic, and Cultural, Legal, Operational and Schedule feasibility
by highlighting their importance ............................................................................................................. 21
2.2 Discuss the components of a feasibility report including structure, intended audience, outcomes .. 27
Task 3 .......................................................................................................................................................... 32
3.1 Provide a summarized description according to the requirements gathered including scope, inputs,
outputs, processes and alternate solutions............................................................................................... 32
3.2 Draw a Level 0 (Context) and a Level 1Data Flow Diagrams and draw a ER Diagram .................. 34
3.3 Create a documentation including background information, problem statements, data collection
process and summary, recommendations, appendices ............................................................................ 37
3.4 Identify user and systems requirements and evaluate how these requirements have been addressed
through your proposed solution .............................................................................................................. 40
How many working hours per day? ........................................................................................................ 40
Conclusion .................................................................................................................................................. 46
Reference .................................................................................................................................................... 47
Appendix ..................................................................................................................................................... 49

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 6 of 56


List of figure

Figure 1- Software Development Life Cycle .............................................................................................. 10


Figure 2-Waterfall model ............................................................................................................................ 11
Figure 3-Spiral Model ................................................................................................................................. 12
Figure 4 -Prototyping Model ...................................................................................................................... 13
Figure 5 -Rapid Application Development ................................................................................................. 14
Figure 6 -Incremental Model ...................................................................................................................... 15
Figure 7 -Agile Model ................................................................................................................................ 16
Figure 8 -Software life cycle model ............................................................................................................ 20
Figure 9 - Slide 1......................................................................................................................................... 21
Figure 10 - Slide 2....................................................................................................................................... 21
Figure 11- Slide 3........................................................................................................................................ 22
Figure 12 - Slide 4....................................................................................................................................... 22
Figure 13 -Slide 5........................................................................................................................................ 23
Figure 14 -Slide 6........................................................................................................................................ 23
Figure 15 -Slide 7........................................................................................................................................ 24
Figure 16 - Slide 8....................................................................................................................................... 24
Figure 17 - Slide 9....................................................................................................................................... 25
Figure 18 - Slide 10..................................................................................................................................... 25
Figure 19 – Slide 11 .................................................................................................................................... 26
Figure 20 - gantt chart for system B ........................................................................................................... 31
Figure 21 - Context Level Data Flow Diagrams ......................................................................................... 34
Figure 22 - Level 1 Data Flow Diagrams ................................................................................................... 36
Figure 23 - ER Diagram .............................................................................................................................. 36
Figure 24 - User interfaces .......................................................................................................................... 43

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 7 of 56


List of Table

Table 1 - Project Feasibility ........................................................................................................................ 28


Table 2 - Time for the project ..................................................................................................................... 28
Table 3 - Cost for system A ........................................................................................................................ 29
Table 4 - Cost for system B ........................................................................................................................ 29
Table 5 - Cost for system C ........................................................................................................................ 30
Table 6 - Alternative solution ..................................................................................................................... 33
Table 7 - Feedback form ............................................................................................................................. 39
Table 8 - Hardware requirements................................................................................................................ 45

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 8 of 56


Acknowledgement

I would like to express my lecture Mr.Indika Sadanuwan for the useful comments. Remarks and
enragement though the learning process of this module.
Furthermore, I would you like to think my friends for the support on the way. And I would you
like to think my loved ones, who have supported me through haut entire process, both by keeping
me harmonious and help me putting pieces together.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 9 of 56


Task 1
1.1 Evaluate range of different lifecycle models with their suitability and suggest which
model best fits the scenario
Software Development Life Cycle

The systems development life cycle (SDLC), also referred to as the application development life-
cycle, is a term used in systems engineering, information systems and software engineering to
describe a process for planning, creating, testing, and deploying an information system.

Include the,

 Waterfall Model
 Spiral Model
 Prototyping Model
 Rapid Application Development Model
 Incremental Model
 Agile Model

The following image is a graphical representation of the various stages of the typical SDLC.

Figure 1- Software Development Life Cycle

Waterfall model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 10 of 56


The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each
phase must be completed fully before the next phase can begin. This type of software
development model is basically used for the project which is small and there are no uncertain
requirements. At the end of each phase, a review takes place to determine if the project is on the
right path and whether or not to continue or discard the project. In this model software testing
starts only after the development is complete. In waterfall model phases do not overlap.
Waterfall Model is closely accord for the Stafford University. The main disadvantages of this
model are we cannot use the requirements change dynamically and we cannot go back during the
life cycle.

Figure 2-Waterfall model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 11 of 56


Spiral Model

The spiral model is a risk-driven process model generator for software projects. Based on the
unique risk patterns of a given project, the spiral model guides a team to adopt elements of one
or more process models, such as incremental, waterfall, or evolutionary prototyping. The spiral
model is similar to the incremental model, with more emphasis placed on risk analysis. The
spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software
project repeatedly passes through these phases in iterations (called Spirals in this model). The
baseline, spiral, starting in the planning phase, requirements are gathered and risk is
assessed. Each subsequent spiral builds on the baseline spiral. It’s one of the software
development models like Waterfall, Agile, V-Model. But in Stafford requirements are fully
aspectual. Sometimes may be its hard to define objective, verifiable milestones. Spiral model is
not suitable for Stafford University.

Figure 3-Spiral Model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 12 of 56


Prototyping Model

Prototyping is the process of building a model of a system. In terms of an information system,


prototypes are employed to help system designers build an information system that intuitive and
easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis
phase of the systems development life cycle. During the requirements determination portion of
the systems analysis phase, system analysts gather information about the organization's current
procedures and business processes related the proposed information system. In addition, they
study the current information system, if there is one, and conduct user interviews and collect
documentation. This helps the analysts develop an initial set of system requirements. There are
some disadvantages also. They are leads to implementing and then repairing way of building
systems, Practically, this methodology may increase the complexity of the system as scope of the
system may expand beyond original plans, Incomplete application may cause application not to
be used as the full system was designed and Incomplete or inadequate problem analysis. This
system is not suitable for Stafford University.

Figure 4 -Prototyping Model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 13 of 56


Rapid Application Development (RAD)

RAD model is Rapid Application Development model. It is a type of incremental model. In RAD
model the components or functions are developed in parallel as if they were mini projects. The
developments are time boxed, delivered and then assembled into a working prototype. This can
quickly give the customer something to see and use and to provide feedback regarding the
delivery and their requirements. They are Requires highly skilled developers, cost is very high
because of modeling and coding cost is too much, and this system requires sufficient human
resources to create right number of RAD team. So RAD is not suitable for Stafford University.

Figure 5 -Rapid Application Development

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 14 of 56


Incremental Model

In incremental model the whole requirement is divided into various builds. Multiple
development cycles take place here, making the life cycle a “multi-waterfall” cycle. Cycles are
divided up into smaller, more easily managed modules. Incremental model is a type of software
development model like V-model, agile model etc. clear and complete definition about whole
system before it is break down or build incrementally. This model is mostly suitable for huge
projects where the requirement not clear, so incremental model is not compatible with Stafford
University.

Figure 6 -Incremental Model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 15 of 56


Agile Model

Agile SDLC model is a combination of iterative and incremental process models with focus on process
adaptability and customer satisfaction by rapid delivery of working software product. Agile Methods
break the product into small incremental builds. These builds are provided in iterations. Each iteration
typically lasts from about one to three weeks, Every iteration involves cross functional teams working
simultaneously on various areas like Planning, Requirements Analysis, Design, Coding, Unit Testing
and, Acceptance Testing. Only senior programmer can take decision during the development process.
There are some problems in documentations and designing. And the final results can take off the track
because customer requirements are not clear. So this model is use when the customer requirement
changes rapidly. But in Stafford University does not have rapidly requirements. Therefore the Agile
development model is not suitable for Stafford University.

Figure 7 -Agile Model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 16 of 56


When we were given the functional requirements of the above-mentioned models and traditional
SDLC is not suitable, this scenario: such as the cascade model and the gradual model. According
to my model cascade perspective has a sequential flow of phases. This means that the stages do
not overlap each other. Therefore, the production team cannot move to the previous stage and
make the changes. According to this scenario, a conflict with the process assigned to the students
of the cycle. Therefore, there is little conflict about the requirements.

This model requires a clear and complete definition of the whole system before it can be divided
and built gradually. Therefore, the graded model does not fit into this scenario because of
inconsistencies in the process that assigns students to courses.

Spiral model is definitely not a suite for this scenario. Because this is the most expensive model
and the success of the project relies heavily on risk analysis. Very specific experience is
required. According to this scenario, this is not a high-risk project. Therefore, if we use this
model, we should spend more money for highly qualified employees. This is a medium-sized
project, and this is not a threat to the high-level project. Therefore, the spiral model is not
suitable for this type of projects.

I suggest a graceful process model is the most suitable model for the SDLC scenario, since it has
the ability to manage the changes until the end of the requirements. Since it is able to adapt to
changing circumstances regularly, in the form of an elegant process, and stressed people and
instead of interaction processes and tools, we suggest best software solutions using agile process
model.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 17 of 56


1.2 Discuss the importance of following a procedural/staged lifecycle in a systems
investigation by providing the link of each stage and highlight their importance

Software Development Life Cycle, SDLC for short, is a well-defined, structured sequence of
stages in software engineering to develop the intended software product. Development Lifecycle
Software (SDLC) is a framework for determining the tasks performed by each step in the
software development process. SDLC is a structure, followed by the software development team
within the organization. Each processes model follows a particular life in order ensure success in
processes of software development.

Software life cycle model describe phases of the software cycle and the order in which those
phases are executed Requirement are translated in to design. Code is produced according to the
design which is called development phases. After coding and development the testing verifies the
deliverable of the implementation phase against requirement, Even though there is various kind
of SDLC models following six phases are identified in every software life cycle model.

1. Requirement gathering and analysis


2. Design
3. Implementation or coding
4. Testing
5. Development
6. Maintenance

Requirement gathering and analysis

Planning: Without the perfect plan, calculating the strengths and weaknesses of the project,
development of software is meaningless. Planning kicks off a project flawlessly and affects its
progress positively. The analysis of requirements is the most important and the most important
stage in SDLC, usually done by the most trained and conversant software engineers in the
organization. After the requirement gathered from the customer, a scope document is created in
which the scope of the project is determined and documented. The feasibility study and an
analysis are then carrying on analysis the validity of gathered information with the requirement
of the system.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 18 of 56


Design
The System and the software design are prepared according to the requirement specifications
identified at the previous stage using the system requirement specification. This assists at define
the overall system architecture and Cleary identify the requirements of the system hardware and
documentation in design document to design document specification. This design document
specification is review by all important stakeholders and the best design approach is selected for
the product. System design is the output of the next phase.

Implementation or coding

The cording is started at this stage after receiving the system design is divided in to modules. A
software developer assigned to work in an allocated part of the work which subs divided under
task allocation according to their skills which lead to an effecting coding. This is the longest
phase in the cycle and main focus of the developer. The programmer follows the coding
guidelines defined by their company and programming tools such as compilers, debuggers are
used to generate code. The different programming languages such as java, C++, HTML, are used
for coding.

Testing

The developing code is it tested against the requirement of justify that the product is actually
fulfill the needs which have gathered at the requirement phase. The functional testing such as
system testing, accepting, unit testing and integration testing and non functional testing are done
at this stage. Quality Analyst tests the developed software or using automates tools. The Quality
Analyst ensures the product is free of errors then it is forwarded to next stage.

Development

The testing successful then the product will be delivered to the client. The beta testing is carried
out by the client. The team will be reported if any bugs are changes are required. The final
development will occur after those reporters are fixed.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 19 of 56


Maintenance

The client are using developing the system, issues can be raised from time to time which need
the solution. The processes changing system after it has been delivered is known as
maintenance.

Figure 8 -Software life cycle model

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 20 of 56


Task 02
2.1 Prepare a PowerPoint presentation to assess the impact of different feasibility criteria a
systems investigation including Technical, Economic, and Cultural, Legal, Operational and
Schedule feasibility by highlighting their importance

Figure 9 - Slide 1

Figure 10 - Slide 2

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 21 of 56


Figure 11- Slide 3

Figure 12 - Slide 4

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 22 of 56


Figure 13 -Slide 5

Figure 14 -Slide 6

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 23 of 56


Figure 15 -Slide 7

Figure 16 - Slide 8

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 24 of 56


Figure 17 - Slide 9

Figure 18 - Slide 10

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 25 of 56


Figure 19 – Slide 11

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 26 of 56


2.2 Discuss the components of a feasibility report including structure, intended audience,
outcomes

Feasibility study determines where the project is feasible to important. The feasibility report is
the documentation of findings and proposal for the system which ensure that the technically,
economically, legally operational and schedules are viable to continue the project.
Executive summary

This project intends to developing automated software as the solution for the limitations of
prevailing manual system at Stafford University. The software team has identified about the this
university structure, users, weakness and issues of the manual system, requirement of the new
system and solutions for the issues and develop alternative system, for Stafford University
system is useful. The requirement analysis universities develop the software requirement
specification.

Review of goals and objectives

 Increase accuracy to 95%


 Increase performance 30%
 Decrease the cost by 20%
 Increase security 99%

System issues

 High operational cost and less effectiveness


 Unauthorized access to manual files
 Work load
 Student service issues
 Time consuming manual based system
 Registration system of the student is not available

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 27 of 56


Project Feasibility

Feasibility Wt System A System B System C


criteria
Schedule 20% 14 months score – 90 18 months score-80 20 Months score- 85

Technical 30% Score-70 Score -90 Score – 80

Operational 20% Only support member Full support user System A is the
requirement score -80 requirement -100 differ little score 68

Economic (cost 20% 4,180 5,070 5,860


to develop)
Human factor 10% Not user friendly Satisfy requirement Not feasible
Score 54 and user friendly
Political / legal 10% As the per system C This ISO stranded Less Stranded

Ranking 100% 71% 93% 65%

Table 1 - Project Feasibility


The three alternative solutions for the propped for Stafford University, According to the weight
on the feasibility criteria, obvious that system B will be the successful alternative which should
be implemented to gain better outcomes to overcome from the current issues of the this
organization profitability by achieving set goals and their objectives.

Time for the project

Activity System A System B System C


Requirement analysis 1 month 3 month 2 month
Design the system 3 month 4 month 5 month
Implementation 3 month 3 month 4 month
Testing 2 month 3 month 4 month
Development 2 month 3 month 3 month
Maintenance 2 month 2 month 2 month
Total 14 month 18 month 20 month
Table 2 - Time for the project

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 28 of 56


Cost for system A

Item Cost (per unit) LKR Number of units Total cost


PC 300 8 2,400
Server 150 1 350
Networking 150 - 150
Printer 50 2 100
Software 200 1 200
UPS 50 8 400
Backup drive 60 2 120
Development 210 - 210
Other 250 - 250
Total 1,620 22 4,180
Table 3 - Cost for system A

Cost for system B

Item Cost (per unit) LKR Number of units Total cost


PC 300 10 3,000
Server 400 1 400
Networking 100 - 100
Printer 70 2 140
Software 200 1 200
UPS 50 10 500
Backup drive 85 2 170
Development 240 - 240
Other 270 - 270
Total 1,765 26 5,070
Table 4 - Cost for system B

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 29 of 56


Cost for system C

Item Cost (per unit) LKR Number of units Total cost


PC 400 8 3,200
Server 500 1 500
Networking 150 - 150
Printer 70 3 210
Software 250 1 250
UPS 100 8 800
Backup drive 85 2 170
Development 275 - 275
Other 295 - 295
Total 2,125 27 5,850
Table 5 - Cost for system C
Project benefits

 The new system also reduces operational


 Provides better security levels
 Barak down of report and system analysis part become simple and easy
 Reduce paper usage
 An automated system helps the management level to make the better decisions.
 This system gives to more accurate and relevant data
 Proper data handing of student details, course details and other details with ease of entering
adding, editing, deleting retrieve and analyzing data at minimum cost and time.

Recommendation

 The staff should be will trained for this new operating system.
 This organization has to be purchase need technology.
 Network connection should be setup and render the service provider.
 Hire of training the staff and developing the software.
 This organization has to automate the system in “B”.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 30 of 56


Conclusions

 The staff member has basic knowledge in IT needs training for better results.
 The Stafford University is the advance technical equipment and want be purchase
 Experience employees in IT should be joined to the organization.

Gantt Chart for system B

Figure 20 - gantt chart for system B

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 31 of 56


Task 3
3.1 Provide a summarized description according to the requirements gathered including
scope, inputs, outputs, processes and alternate solutions
Scope
The new system will automated the department of Stafford University in a management system.
The major department can be identified as administration, customer service, human resources
and finance.

Input

The data enter in to the system is an input. All input should be checked. If the user is entering
improper or invalid data appropriate error messages should display and ask the user correct them.
Student registration details given by the student during they log in to the system should be in the
database. The online- registration from all mandatory fields should be filled otherwise display
error message.

 The user identity, password, user name, emails sending Stafford University by student, rating
feedback after receiving register courses for them this university.
 Input data new student registration, modification of editing student details response to email
from student, add new course, and add new lectures details and promotion and discount on
bulk purchasing.

Output

The information produced by the system after processes input are output.

 Registration student details


 Payment invoice and the email confirming the payment for the resisted courses.
 Error messages such as” password should be at least ten digits” ,”invalid data” .
 Warnings and alerts.
 Course Schedules and course catlog

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 32 of 56


Alternative solution

The Alternative solution have rank from according to their feasibility in the system as follow

Feasibility Criteria System A System B System C

Technology feasibility 4 5 4

Economical feasibility 3 4 2

Legal feasibility 2 5 3

Operational feasibility 4 5 3

Schedule feasibility 5 4 3

Total 18 23 15

Table 6 - Alternative solution


1 – Very poor 2 – poor 3- Average 4 – Good 5 – very Good

Above the table this system B is the most reliable, most suitable and successes system to be
implemented among the alternative system.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 33 of 56


3.2 Draw a Level 0 (Context) and a Level 1Data Flow Diagrams and draw a ER Diagram

Context Level Data Flow Diagrams

Figure 21 - Context Level Data Flow Diagrams

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 34 of 56


Level 1 Data Flow Diagrams

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 35 of 56


Figure 22 - Level 1 Data Flow Diagrams

ER Diagram

Figure 23 - ER Diagram

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 36 of 56


3.3 Create a documentation including background information, problem statements, data
collection process and summary, recommendations, appendices

We develop this system is to a university, is a well-known university in the country which offers
reputed degrees to the students and have more faculties in the universities. On this university is
that system is manually and the student too have to fill their details on paper and hand it over to
the registrar which creates a mess because with the time the documents can weathered or
misplaced etc, this problems the university have decided to introduce system to work with, so the
work will be efficient in the process.

the new system are to make the work easy at Stafford university it have the ability to work more
efficiently, the students able to inserts to data into the system where the registrar will verify .they
give the confirmation to the system about the data inserted the lectures can publish the results of
the student on the every student can check their results through the system.

We talk about the efficient of the system there is also draw backs with the system, the company
will face a problem for trained the users, the software is new there will be more work needed to
the admin to trained and make the standard of the users.

The admin team have experience in managing the system because they also new to the system
the team also will take time to get experienced on the system.

We have gathered to information on the system how the system is handled and the feedback from
the user which uses the system.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 37 of 56


Recommendation

The system understudy administration work, we can relegate another course, yet the issue is that
this is a fundamental slip-up in my enlistment framework. Along these lines, the systems create
up this framework as we can embed subject likewise for every course. Adding a subject as well,
this creates clients can look effortlessly what are the subjects under important course.

It is exceptionally import assignment for such training foundation that keeping reinforcements of
the database, in light of the fact that colossal number of understudy are contemplating in this
college and every one of the points of interest of them are spared in the database which the
product has been associated. Damage happens to the server or information, throughout the
everyday issues of the college will stifle clients proposed that having a method for getting
reinforcements by this system.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 38 of 56


Feedback form

Name: ……………………………………………………………………………………..

Totally Satisfied Dissatisfied Totally Average


satisfied Dissatisfied
1. User friendly

2. Easy install

3. Security system

4. You can recommend


this software others
5. Navigation though
functions
6. How is the user
manual?

6. Member and book


details view facility
7. Member and book
details update facility
8. Member and book
details search facility
9. Member and book
delete facility
10. Your suggestion for the this system

Table 7 - Feedback form

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 39 of 56


3.4 Identify user and systems requirements and evaluate how these requirements have been
addressed through your proposed solution

Types of requirement

User requirement

This idea to the user how the system is done and its functions written in natural language which
the user can understand so we arranged a meeting with the respective registrar in the university
to get more information of the system we need to develop for the software.

 What type of system?


 A student management system
 What type of system is currently in use?
 Manual system
 How many students are currently studying in the university?
 Nearly 20000 students
 How many new students register per intake?
 Nearly 800 – 1000
 How much staff works in handling data?
 About 50
 How many lecturers are there?
 About 50
 Does updating occur in the current manual system? , If so is it easy to perform?
 Yes updating happens but it is very hard

How many working hours per day?


 10 working hours
 Does the university contain a website?
 Yes we do have a website
 When does the university give holidays for the students? And for how long?
 Around June every year for around three months

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 40 of 56


 What kind of operating system is the staff normally used for?
 Windows 7 operating system
 Would u prefer if any new resources were bought from the outside and fixed inside the
University?
 Yes anything which is a part of the system which is to be built.
 Would you like us to give a small training to the staff before they use the system?
 Yes that would be good
 Would you prefer a security system with usernames and passwords to log into computers?
 Yes that would be a good thing so only authorized people will be given access.
 Does the university have a network? If not would u like us to set one up?

Software Requirement
The student Management system which is been built for the Stafford University
Purpose
The purpose of Student Management software for Stafford University, This document wills the
complete declaration of the development of this system. It will also explain system constraints,
user interfaces and interactions with other applications. This system is there to be proposed to the
client for the approval for developing the first version of the software
Scope
Stafford University will be able to register the students through the system. It include course
details are also allowed to be accessed through the system as well the details then can be
authenticated by the register in the university to confirm the student details are correct according
to the information. The lectures can give their subject material through the system. exams results
also be released to that particular student through the system so that they can access through the
system whether they has passed the exams.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 41 of 56


Addresses direct processes of the system or information the system need to contain.

Search facility

This enable user to enter search context on the screen, select multiple options on the search
display all the course based on search, enable user navigate between search result and notify the
user when course product is not found.

User profile

The system wills all users create name and password for the profile, update profile information
such as course details, billing details about select course and display course catlog.

User characteristics

Types of users that will use this system, each of these users use the system in different ways and
so they all have different requirements.
 Students
 Staff members
 Admin
Students can use this system to mark their attendance or search their record out to check the
details. Register use the system to update the records of a student or any other activity is done.
Admin use the system to fix an error and maintain the system to make sure the system runs
without any errors
Invoices

The system will be display detailed invoice for course fee it is confirmed and allow user print it.

Payments

The system will display available payment method, allow user to select method and enable user
pay for the courses.

Change and cancellation of details

The system change will display the course details that can be changed allow users to change or
cancel the course.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 42 of 56


User interfaces
The certain record there will be options by clicking on them will help to make changes to the
records and update them. The staff member can to login to the system. System will view to enter
the username and password.

Figure 24 - User interfaces

Hardware interfaces

Hardware interface consists of a computer is connected to the network by the use of LAN cable
Software interfaces

This software is what is installed in the computer with communicates with the other hardware
components which make up the system.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 43 of 56


Non functional requirement

Performance requirement

This software is web based it requirement a powerful server machine with high band internet
access. Server machine possesses a powerful central processing unit. The enable to handle
multiple users at the same time, higher storage space allow best performance. The product will
take initial loading time depending on internet strength which depends on the media from which
the product run and performance also depend on hardware component of the client.

Operational requirement

The physical and technical requirement in which the system operates is defined under these
criteria. The system should be cost effective within the budgets margins and able to integrate
with this system run in the business. It also is performing on any web browser.

Security requirement

Security requirement equipped with virus guards and firewalls to block any viruses software
from harming the system and also each authorized staff member is granted a unique username
and password in order to prevent unauthorized access.

Maintainability requirement
This system use to be once every five months to check if there are any errors or corrupted files in
the system, which is slowing down the work, and if there are any they are removed.

Availability
The system availability every day at any time (24/7), But it will not be available if the server is
down for maintenance. And maintenance occur only once per five months
Logical database requirements
The logical database requirement is an essential requirement when building the system as this
system handles mainly used in storing student data. The storage capability of the system will be
put at maximum (e.g. 5 TB Hard disk) as records will be stored. The data stored will be in the
Microsoft office word format (.docx) and also the data will be held in a NTFS (New Technology
File System) formatted hard disk.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 44 of 56


Hardware requirements

Processor Intel® Core i3-4130T Processor


(3M Cache, 2.9 GHz)
Graphics card Intel HD graphics 4400 inbuilt in CPU
Ram Kingston FURY Memory White - 4GB Module - DDR3
1600MHz CL10 DIMM
Motherboard FOXCONN H81MX
Hard disk Samsung MZ-7TE1T0BW 750 GB
Monitor 19-inch View sonic LED monitor
Disk drive Samsung SH-222BB/BEBE
Casing Bit Fenix Pandora Core Micro ATX mid tower

CPU cooler Akasa Venom Medusa


Keyboard Logitech wireless keyboard K360

Power supply FSP Aurum CM 750W 80+ Gold Modular


Mouse Logitech wireless mouse M325

Table 8 - Hardware requirements

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 45 of 56


Conclusion

The student management system for Stafford University as scenario was given with the
information of how the work inside Stafford University is run. the development of the system a
system requirement specification documentation was made and a feasibility study was done and
a report was created. The concluded that the development model best fit for the development of
the system is the Iterative waterfall model. And by using this development of the model should
take place and in each stage of development the quality should be kept to the maximum as
quality management techniques are used throughout the development life cycle.

The System Analysis and Design subject the main area we learn about is the analysis part which
is demonstrated by the creation of and SRS documentation and a feasibility report and analysis
helps us understand the requirements of a certain system to be made.

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 46 of 56


Reference

What is Iterative model. (2015). What is Iterative model- advantages, disadvantages and when to
use it?. [ONLINE] Available at: http://istqbexamcertification.com/what-is-iterative-model-
advantages-disadvantages-and-when-to-use-it/. [Accessed 3 February 2018].

SDLC Waterfall Model. (n.d). SDLC Waterfall Model. [ONLINE] Available at:
http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm. [Accessed 2 February 2018].

Margaret Rouse. (2007). What is waterfall model? - Definition from WhatIs.com. [ONLINE]
Available at:http://searchsoftwarequality.techtarget.com/definition/waterfall-model. [Accessed 5
February 2018].

Margaret Rouse. (2007). What is spiral model (spiral lifecycle model)? - Definition from
WhatIs.com. [ONLINE] Available
at:http://searchsoftwarequality.techtarget.com/definition/spiral-model. [Accessed 4 February
2018].

What is Prototype model?. (n.d). What is Prototype model- advantages, disadvantages and when
to use it?. [ONLINE] Available at: http://istqbexamcertification.com/what-is-prototype-model-
advantages-disadvantages-and-when-to-use-it/. [Accessed 6 February 2018].

Chandra venapoosa. (2012). The Evolutionary Prototyping Model | IT Training and Consulting –
Exforsys. [ONLINE] Available at: http://www.exforsys.com/career-center/project-management-
life-cycle/the-evolutionary-prototyping-model.html. [Accessed 9 February 2018].

What is RAD model. (n.d).What is RAD model- advantages, disadvantages and when to use it?.
[ONLINE] Available at: http://istqbexamcertification.com/what-is-rad-model-advantages-
disadvantages-and-when-to-use-it/. [Accessed 10 February 2018].

What is Agile model?. (n.d). What is Agile model – advantages, disadvantages and when to use
it?. [ONLINE] Available at: http://istqbexamcertification.com/what-is-agile-model-advantages-
disadvantages-and-when-to-use-it/. [Accessed 12February 2018].

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 47 of 56


Russell Kay. (2002). System Development Life Cycle | Computerworld. [ONLINE] Available
at:http://www.computerworld.com/article/2576450/app-development/system-development-life-
cycle.html. [Accessed 8 February 2018].

Ronda Bowen. (2013). Explaining the Different Types of Feasibility Studies. [ONLINE]
Available at:http://www.brighthubpm.com/project-planning/56372-types-of-feasibility-studies/.
[Accessed 19 February 2018].

What is quality management?. (n.d). What is quality management? definition and meaning.
[ONLINE] Available at:http://www.businessdictionary.com/definition/quality-management.html.
[Accessed 19 February 2018].

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 48 of 56


Appendix

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 49 of 56


PRESENTATION EVALUATION FORM

Context – This presentation assessment criteria sheet makes provision for the assessment of student
engagement with the group and the handling of questions. The different features of the assessment
criteria can be adjusted and given different weightings in the overall grid as required.

Subject- Student/s, Name/s-

Excellent Very Good Meets Below


Good Standard Standard

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 50 of 56


Information Detailed Detailed Generally Limited Very Limited
Accurate Accurate accurate knowledge with many
Relevant Relevant and with some errors and
Highlight relevant, significant gaps
the key but some gaps and/or
points gaps and/or errors
irrelevant
material
Structure Rigorously Generally Not always Argument Muddled,
argued, clearly logical may underdevelo incoherent
Logical, argued be overly ped and not
easy to and influenced clearly
follow logical by mentioned
secondary
literature
rather than
the
requirement
of the topic
Interpretation Extensive Attempts Little Fairly Entirely
evidence to go attempt to superficial derivative
of beyond go beyond and Generally
independ the ideas or criticize generally superficial
ent presented secondary derivative
thought in the literature and
and secondary uncritical
critical literature
analysis
Use of Key points Most Some Some Little or no
Evidence supported points illustrative evidence evidence
with illustrated material, mentioned, discussed
evidence, with but not but not
critically relevant critically integrated
evaluated evidence evaluated in to
presentatio
n or
evaluated

Presentation Clearly, Generally Conveys Not always Clumsy,


skills Lively, clear and meaning, clear or easy disjointed,
Imaginativ lively, use but to follow, difficult to
e, good of sometimes unimaginati follow dull
use of appropriat unclear or ve and not
visual aids e visual clumsy engaging

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 51 of 56


aids
Time Perfectly Well More or less Significantly Significantly
Management timed well organized, right length, over time, under or
organized more or but some material overtime,
less to materials fairly clearly have
time not covered disorganized not tested
properly as and rushed out material
a result of beforehand,
overruns by disorganized
five minutes
or more

Best Features-

Suggestions to improve-

Assessor- Date-

IV- Date-

Hansani Chathurani SYSTEMS ANALYSIS AND DESIGN Page 52 of 56


Possible
Outcomes/Criteria for PASS Page Feedback
evidence
LO1 Understand different systems life cycles
1.1 Evaluate different systems lifecycle models Task 1.1

1.2 Discuss the importance of following a Task 1.2


procedural/staged lifecycle in a systems
investigation
LO2 Understand the importance of a feasibility study
2.1 Discuss the components of a feasibility report Task 2.2

2.2 Assess the impact of different feasibility criteria Task 2.1


on a systems investigation

LO3 Be able to perform a systems investigation


3.1 Undertake a systems investigation to meet a Task 3.1
business need

3.2 Use appropriate systems analysis tools and Task 3.2


techniques to carry out a systems investigation

3.3 Create documentation to support a systems Task 3.3


investigation
3.4 Evaluate how user and systems requirements Task 3.4
have been addressed.

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 53 of 56


Grade Descriptor for MERIT Possible evidence Feedback
M1 Identify and apply strategies to find appropriate Task 1.1
solutions
Clearly justify by making judgments
M1.1 Effective judgments have been made to select the most suitable process
model which fits to the scenario.

M2 Select / design appropriate methods / techniques


Proper use of Harvard
M2.3 A range of sources of information has been used referencing has been used and
considerable amount of
references have produced from
different sources. Use of correct
in text citations and the end list
references.

M3 Present and communicate appropriate findings Documentation is well structured


adhering to the formatting
M3.1The appropriate structure and approach has been used guidelines with non-overlapping
facts.
Data provided are accurate,
reliable and consistent.

Grade Descriptor for DISTINCTION Possible evidence Feedback

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 54 of 56


D1 Use critical reflection to evaluate own work and Task 1.1
justify valid conclusions
Evaluate range of different life cycle
D1.1Conclusions have been arrived at through synthesis of ideas models and provide a valid
and have been justified conclusion on which model best fits
the scenario.

D2 Take responsibility for managing and organizing


activities
Gantt chart provided at the
D2.3activities have been managed appendix section and submit the
work on time

D3 Demonstrate convergent / lateral / creative Task 3.4


thinking User and systems requirements
have been identified and evaluated
D3.4 problems have been solved.

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 55 of 56


Strengths: Weaknesses:

Future Improvements & Assessor Comment:

Assessor: Signature: Date: ____/____/______

Internal Verifier’s Comments:

Internal Verifier: Signature: Date: ____/____/______

All rights reserved ©ESOFT Metro Campus, Sri Lanka Page 56 of 56