Project Work Answers of System Operational Capabilities- PROG7311

Project Work Answers of System Operational Capabilities- PROG7311

Contents
Introduction ………………………….. ………………………….. ………………………….. ……………………. …

Preview text

Contents
Introduction ………………………….. ………………………….. ………………………….. ………………………….. ….. 2
Non -function requirements ………………………….. ………………………….. ………………………….. ……… 2
Desi gn patterns and architecture patterns ………………………….. ………………………….. ………………. 3
Conclusion ………………………….. ………………………….. ………………………….. ………………………….. .. 3
References ………………………….. ………………………….. ………………………….. ………………………….. … 4
Introduction
Non -function al requirements are the specifications used in describing the system’s operational
capabilities and the constraints used to enhance the system’s functionalities (Ameller et
al.,2018 ). They may include speed, reliability, security and the general usability of the system.
They are fundamental aspects of the system. Without them , the system can be vulnerable to
various attacks , and it won’t be appealing to the user. This report outlines multiple non –function
requirements for any given system and their importance.
Non -function requirements
As st ated before , non -functional requirements are fundamental aspects that must be implemented
in any given system. They are essential in such a way that they make or break the success of any
given scenario . The user of any given system shall not hesitate to re ject a system if it does not
meet some essential qualities like the lack of security features and low performance. The
following are some of the non -functional requirements required in the system.
ï‚· Security, any given software must remain resilient in case of an attack (Jha and
Mahmoud , 2019 ). The behaviour of any provided software must be correct and
predictable. It has to be reliable and behave normally even if we have a DDOS attack. It
has to ensure the integrity of the customer information. This featur e will be implemented
in the section of the system. The user shall have to provide the correct username and
password for them to be able to access and use the system. The passwords and usernames
shall be encrypted , and no one shall have access to their plain texts. Users shall also have
to be verified if they move from one system module to another. This will ensure the
integrity and confidentiality of all the user information.
ï‚· Usabi lity is a feature that passives how to use the system. This feature can reduce the cost
of training some users on using the system (Washizaki ., 2022 ). It shall be done on the
system by using user -friendly interfaces and showing messages to the user if we have any
errors.
ï‚· Performance is the mechanism used to measure employee performance of any given
system measurably . The system shall be able to locate information of all the users that
have login into the system and what they have done with the system. This will keep track
of all the activities that are taking place in the sys tem for future use
These features have a small impact on how the system shall be developed. The developer
shall have to find suitable ways of implementing them in the required manner.
Design patterns and architecture patterns
They are mainly used in accele rating the development process (Kim, Mor itz and Hullman, 2021) .
They provide proven paradigms that have been implemented and tested . N ew ones shall not be
invented , thus speeding up the application’s development process . The most important reason for
using the design patterns is that they provide a general solution that does not require specific ties
to a particular problem. These designs shall be necessary for implementing our system since they
can easily be used in each stage . This will also increase the development process since we shall
be using the proven solutions, and we shall not have to make our solutions to solve issues in the
program.
Conclusion
In conclusion , implementing non -functional requirements to any given system increases the
system’s quality, and customers shall also be assured of information security and confidentiality.
On the other hand , design patterns make the development process more accessible since the
dev elopment uses existing procedures and have been proven to be working.
References
Ameller, D., Burgués, X., Costal, D., Farré, C. and Franch, X., 2018. Non -functional
requirements in model -driven development of service -oriented architectures. Science of
computer programming , 168 , pp.18 -37.
Jha, N. and Mahmoud, A., 2019. Mining non -functional requirements from app store
reviews. Empirical Software Engineering , 24 (6), pp.3659 -3695.
Kim, H., Moritz, D. and Hullman, J., 2021, June. Design Patterns and Trade‐Of fs in Responsive
Visualization for Communication. In Computer Graphics Forum (Vol. 40, No. 3, pp. 459 -470).
Washizaki, H., Khomh, F., Guéhéneuc, Y.G., Takeuchi, H., Natori, N., Doi, T. and Okuda, S.,
2022. Software -Engineering Design Patterns for Machine L earning
Applications. Computer , 55 (3), pp.30 -39.

QUALITY: 100% ORIGINAL PAPER – NO PLAGIARISM – CUSTOM PAPER
error: Content is protected !!