Systems Analysis and Design for Nuk Restaurant System Project

Verified

Added on  2023/01/10

|11
|3012
|77
Project
AI Summary
This project provides a detailed analysis of the Nuk Restaurant System (NRS), a restaurant opened in 2020. The study begins by defining the aim and objectives of the NRS project, which focuses on systematically collecting customer data and tracking sales. It then explores the Systems Development Life Cycle (SDLC), detailing each phase from planning and analysis to design, development, testing, and maintenance, to develop the NRS project. The project also includes the development of a Work Breakdown Structure (WBS) to manage project tasks, and the creation of a Critical Path Method (CPM) and Program Evaluation and Review Technique (PERT) chart to identify the critical path and project timeline. Finally, the project calculates financial metrics, including Net Present Value (NPV) and payback period, to evaluate the project's financial viability. The analysis offers a comprehensive overview of project management and system development principles, providing insights into the development of high-quality information systems.
Document Page
INTRODUCTION
Systems Analysis and Design is useful in describing the key methodologies which is
significant in the development of the high degree of quality information system. This is useful in
transforming data and combining information technology, data and the people in order to support
the requirement of the business. This study will highlight on clearly defining the aim and
objectives associated with the study. The Systems Development Life Cycle is significantly
required to develop the NRS project. Further this study will also develop the effective work
breakdown structure and PERT or CPM chart to to examine the critical part which has been
required to finish the set project on a timely manner. Lastly, this study calculates the NPV,
payback period and ROI.
MAIN BODY
1. Clearly defining the aim and objectives associated with the study.
Background of Nuk Restaurant System (NRS)
The NUK is considered to be as a restaurant which has been opened up in the year 2020.
The key owners i.e., Mala and Ashli has opened up the restaurant after graduating from the
university. Mala and Ashli tends to run testable procedures related with the online system. The
testable procedures has been carried out significantly in order to analyze and remove the bugs
before launching the system. Nuk Restaurant System helps in keeping the information of the
customers within an online system. This system is also useful in recording the number of tables
which has been booked and key information associated with the special events.
Aim
“The NUK aims at collecting the data from the prospective customers in a systematic
manner by keeping the track of the individual sales, popular food and drink and loyal
customers.”
Objective
To create an account of the customers which comprises of first and last name, city,
mobile number, zip code, residential address and email address.
To create unique identification number for each customers.
To integrate online system in NUK which helps in keeping the key information
associated with the name and type of services availed by the customers.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
The development of the Nuk Restaurant System is highly significant because it helps in
the better attainment of the goals and objectives of the NRS project. It is useful in completing
the task in an automated manner and helps in attaining higher operational goals and
sustainability. Keeping all the key information about the customers is of key relevant
importance.
2. Analysing the Systems Development Life Cycle to develop the NRS project.
Systems Development Life Cycle is one of the key conceptual model which is significant
in managing the organizations operational, informational and the management requirements of
the company (Singletary and Baker, 2019). It is one of the key significant problem solving
technique which helps in improving the system and leads to the attainment of the key aims and
objectives of the company. Systems Development Life Cycle is one of the key significant
framework which defines the framework which mainly comprises of the 6 phases such as
planning, analysis, design, development and implementation, testing and maintenance.
Planning: At this phase, it is crucial to create a Nuk Restaurant System which helps in
significantly evaluating the key problems, objectives and resources which helps in creating the
significant in maintaining the key information system (Belikov, Rogozov, and Shevchenko,
2018, April). The management of the company also focuses on examining the key alternatives in
order to select the best possible way to improve the functioning of the NUK. The management of
the company tends to completely analyse the key requirements of the NUK. The management
wants to develop a system which keeps track of the individual sales, popular food and drink and
loyal customers in a restaurant. This is a stage where the NRS project is brought into the process
to improve the working of the NUK.
Analysis: The feasibility analysis of the project will be analysed crucially which helps in
effectively evaluating whether it is economically, socially, organizationally and technologically
feasible. Complete analysis of the system which has been selected from the wide range of
alternatives has been taken into consideration (Kramer, 2018). It is significant in evaluating the
key functions of the systematic manner. All the key requirements related with the technical and
functional requirements in turn has been significantly taken into consideration physically and
logically. It is significant in analysing the reason for the selection of the Nuk Restaurant System.
Design: At this phase, all the requirement of the customers has been taken into
consideration significantly and is highly useful in defining the elements related with the study. It
Document Page
is useful in examining the key components such as security levels, modules and architectures in a
detailed and expanded manner (Busbee, 2018). It is useful in building the architecture for the
project. Effective software will be developed which helps in improving the functioning of the
Nuk Restaurant System. Use of the POS software is significant in managing the point of sales
structure, accounting, inventory, etc. It helps in automating the work and reducing the work
pressure.
Development and implementation: This is the phase, where the actual task will be
developed and the software tends to start with data recording (Glumich and et.al., 2018,
September). After the development of the effective software associated with the Nuk Restaurant
System then the actual construction of the process has been taken out in order to illustrate the
designs. At this stage the system is finally ready for deploying and is ready to get installed in the
devices of the customers. It is significant in developing a hardware and also leads to
configuration. It helps in developing the business process and system which leads to better
management and better control of the NRS Project.
Testing: At this phase, various range of different elements and sub-system tends to come
together which is useful in effectively introducing the system with varied set of inputs which
helps in analysing if the outputs and the behaviour of the Nuk Restaurant System is synchronized
in a systematic and reliable manner (Shah, 2016). Testing of the Nuk Restaurant System is
significantly performed by the real users or by the specialized set of information technology
team. Testing is useful in evaluating the automated and systematic function which is useful in
examining the actual outcomes in order to attain the key aim and objectives of the Nuk
Restaurant System. It tends to focus on providing embedded security of the data in a significant
cost efficient manner. This phase is useful in creation of the most secure software which leads to
higher operational growth and sustainability with the NRS project. This is the phase where the
aims and objectives of the NRS project must meet.
Maintenance: This is the last phase associated with the Systems Development Life
Cycle. This is the significant phase which ensures that, the system does not become obsolete.
The system will be evaluated on a continuous basis and replace the old hardware with the new
one in order to perform better functions (Sharma, and Misra, 2017). It must comply with the
latest technologies and right standards in order to protect the valuable information of the
customers from current society threats. Continuous development of the Nuk Restaurant System
Document Page
is useful in providing the latest updates and also meet the requirements of the NUK and
customers by significantly meeting the right standards. It helps in improving the quality of the
system. It is highly significant in boosting up the performance and it also helps in adding new set
of capabilities to meet additional user requirement.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
3. Developing WBS structure
WBS refers to the method in getting the complex and multi project done in right way. It
is the manner to conquer and divide larger projects so that the firm could have done the things in
faster and efficient way. It is the tree hierarchical structure which outlines and breaks the project
into smaller portions and manageable portions. An entity could build WBS through creating
folders and the sub-folders and could go further for dividing the individual tasks into the sub-
tasks. The main aim of WBS is making large project as more manageable. Breaking it into the
smaller chunks means as work could be done in simultaneous way by the different members of
the team, resulting to better productivity within the team and makes the project management
easier. It provides the details and information relating to the task performed in each of the
activity with appropriate timelines and duration.
Task Mode Task Name Duration Start Finish Predecessors WBS
1 Initation 20 days Thu 7/9/20 Wed 8/5/20 1
1.2 App development 20 days Thu 7/9/20 Wed 8/5/20 1.1
2 Planning 15 days Thu 8/6/20 Wed
8/26/20 2
2.1 Initiation or
developing alternatives 15 days Thu 8/6/20 Wed
8/26/20 1 2.1
3 Execution 15 days Thu 8/6/20 Wed
8/26/20 3
3.1 Testing of App 15 days Thu 8/6/20 Wed
8/26/20 1,2 3.1
4 Monitoring and
controlling 15 days Thu 8/27/20 Wed
9/16/20 4
4.1 Evaluation of App 10 days Thu 8/27/20 Wed 9/9/20 3 4.1
4.2 Analysis of Bug \ 12 days Thu 8/27/20 Fri 9/11/20 3,4 4.2
4.3
Taking corrective
measures for removing
bug
15 days Thu 8/27/20 Wed
9/16/20 4 4.3
5 Closure 18 days Thu 8/27/20 Mon
9/21/20 5
5.1 Final testing 8 days Thu 8/27/20 Mon 9/7/20 6 5.1
5.2 Launching App 3 days Thu 9/17/20 Mon
9/21/20 7 5.2
4. Developing CPM and PERT
Task
Mode Task Name Duration Start Finish Predecessors Early
Start
Early
Finish
Late
Start
Late
Finish
1 App 20 days Thu Wed Thu Wed Thu Wed
Document Page
development 7/9/20 8/5/20 7/9/20 8/5/20 7/9/20 8/5/20
2
Initiation or
developing
alternatives
15 days Thu
8/6/20
Wed
8/26/20 1 Thu
8/6/20
Wed
8/26/20
Thu
8/6/20
Wed
8/26/20
3 Testing of
App 15 days Thu
8/27/20
Wed
9/16/20 1,2 Thu
8/27/20
Wed
9/16/20
Thu
8/27/20
Wed
9/16/20
4 Evaluation
of App 10 days Thu
9/17/20
Wed
9/30/20 3 Thu
9/17/20
Wed
9/30/20
Thu
9/17/20
Wed
9/30/20
5 Analysis of
Bug \ 12 days Thu
10/1/20
Fri
10/16/20 3,4 Thu
10/1/20
Fri
10/16/20
Wed
10/21/20
Thu
11/5/20
6
Taking
corrective
measures for
removing
bug
15 days Thu
10/1/20
Wed
10/21/20 4 Thu
10/1/20
Wed
10/21/20
Thu
10/1/20
Wed
10/21/20
7 Final testing 8 days Thu
10/22/20
Mon
11/2/20 6 Thu
10/22/20
Mon
11/2/20
Thu
10/22/20
Mon
11/2/20
8 Launching
App 3 days Tue
11/3/20
Thu
11/5/20 7 Tue
11/3/20
Thu
11/5/20
Tue
11/3/20
Thu
11/5/20
Document Page
Critical path:
Path 1: 1 + 2 + 3 + 4 + 6 + 7 + 8
Duration: 20 + 15 + 15 + 10 + 15 + 8 + 3
= 86
Path 2: 1 + 3 + 4 + 6 + 7 + 8
Duration: 20 + 15 + 10 + 15 + 8 + 3
= 71
The Second path is considered as the critical path as it is taking less time to finish the project that
is 71 days.
5. Calculating NPV and payback period
Years
No. Category 0 1 2 3 4 5
1
Value of
benefits $ 8000 $ 8000 $ 8000 $ 8000 $ 8000
2
Developme
nt Cost $ -20000 $ 750 $ 800 $ 770 $ 750 $ 730
3
Annual
expenses $ 2000 $ 2000 $ 2000 $ 2000 $ 2000
4
Net
benefit/cos
ts $ 20000 $ 5250 $ 5200 $ 5230 $ 5250 $ 5270
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
5
Discountin
g factor 1 0.63 0.39 0.24 0.15 0.1
6 NPV $ -20000 -12106.97
7
Cumulativ
e NPV $ -20000 3.5 years
Years Cash inflows ($) Discounting factor
Discounted cash
inflows ($)
1 5250 0.63 3281.25
2 5200 0.39 2031.25
3 5230 0.24 1276.86
4 5250 0.15 801.09
5 5270 0.10 502.59
Sum of discounted cash
inflows 7893.03
Intial investment 20000
NPV -12106.97
Interpretation- The above table represents an analysis of Net present value accounted as
-12106.97 which shows the negative value. It has been stated that positive value of NPV reflects
that the project would be profitable and negative value depicts the losses (Alkaraan, 2017).
Therefore, it has been analysed from this evaluation that the costs of project is very high which
reduces net profits and the firm will incur losses in future as its initial outlay is too higher than its
inflows.
Years Cash inflows Cumulative cash inflows
1 5250 5250
2 5200 10450
Document Page
3 5230 15680
4 5250 20950
5 5270 26220
Initial investment 20000
Payback period 3
0.5
Payback period 3.5 years
Interpretation- The above results reflects that the payback period for the project
ascertained as 3.5 years. As stated longer the period of payback, long time the project would take
in covering the company's initial cost (Adebimpe and Bashir, 2018). However, shorter payback
results to short time the proposal will take in covering initial outlay of an entity. The analysis
shows that the proposal would take longer time equating to 3.5 years for recovering the cost of
an enterprise which clearly indicates that the project is not viable for the company.
Years Net profit
0 -20000
1 5250
2 5200
3 5230
4 5250
5 5270
ROI 9.72%
Interpretation- The above assessment shows that the return on investment for the five-
year periods evaluated as 9.72%. Higher the return, better it is for the company which means
that if higher return on investment is attained, this depicts that performance of the firm would be
improved and it would be earning higher amount of profitability. From an evaluation, it has been
stated that by making an investment in this proposal, an entity will not be generating higher
returns to the future periods.
Document Page
Overall, the table shows reflects that Nuk should not invest in such project as its
development cost and the annual expenses resulted as very high. Moreover, the initial investment
cost is also seen as higher that is $20000. Therefore, it is been stated that the project is not
feasible, desirable and viable for the firm and it must not opt for investing in such kind of the
proposals which incur losses.firm and it must not opt for investing in such kind of the proposals
which incur losses.
CONCLUSION
The above report concludes that the system development life cycle enables in alleviating
complexity in developing the system information system from the zero base within a framework
of the structured phases which assist in shaping the project and in managing it in simple and easy
manner. Moreover, WBS helps in analysing the time taken by each activity along with indicating
the starting of other activity after completion of prior activities depicted in terms of the
predecessors. The technique like PERT and CPM helps greatly in completing several jobs on the
schedule. It minimizes the production delays, conflicts and the interruptions which are counted
as very useful in coordinating various types of jobs of total project & thereby expediting or
achieving project completion within the specified or set time-frame. Investment appraisal
techniques like NPV and payback helps in analysing the performance of the project and in
depicting the viability, desirability, feasibility of the proposal in efficient and effective way. It
helps in assessing that the project would be generating profits or will incur losses in the future
periods.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
REFERENCES
Books and journal
Adebimpe, O. A. and Bashir, O., 2018. Modern Approach to Property Development
Appraisal. Covenant Journal of Research in the Built Environment.
Alkaraan, F., 2017. Strategic Investment Appraisal: Multidisciplinary Perspectives', Advances
in Mergers and Acquisitions (Advances in Mergers & Acquisitions, Volume 16).
Belikov, A.N., Rogozov, Y.I. and Shevchenko, O.V., 2018, April. Synthesis of the life cycle
stages of information systems development. In Computer Science On-line
Conference (pp. 331-337). Springer, Cham.
Kramer, M., 2018. Best practices in systems development lifecycle: An analyses based on the
waterfall model. Review of Business & Finance Studies, 9(1), pp.77-84.
Singletary, V. and Baker, E.L., 2019. Building Informatics-Savvy Health Departments: The
Systems Development Life Cycle. Journal of Public Health Management and
Practice, 25(6), pp.610-611.
Busbee, K.L., 2018. Systems Development Life Cycle. Programming Fundamentals.
Glumich, S and et.al., 2018, September. BP: Integrating Cyber Vulnerability Assessments
Earlier into the Systems Development Lifecycle: A Methodology to Conduct Early-Cycle
Cyber Vulnerability Assessments. In 2018 IEEE Cybersecurity Development
(SecDev) (pp. 77-84). IEEE.
Shah, U.S., 2016. An excursion to software development life cycle models: an old to ever-
growing models. ACM SIGSOFT Software Engineering Notes, 41(1), pp.1-6.
Sharma, A. and Misra, P.K., 2017. Aspects of enhancing security in software development life
cycle. Advances in Computational Sciences and Technology, 10(2), pp.203-210.
chevron_up_icon
1 out of 11
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]