Assignment

profiledloand
Nonfuctionalpropertiesofasytem.docx

Running head: NONFUNCTIONAL PROPERTIES 1

NONFUNTIONAL PROPERTIES 2

Nonfunctional properties

Tom Anderson

Professor Haseltine

February 28, 2021

Introduction

The changing world technology is dictating the normal running of events, including the Education sector. There is a need for a system that would match these advancements and make the operations successful. It, therefore, calls for the collectivity to see its effectiveness and the possible degree of efficiency. These systems should also be safe and secure and able to deal with risks from without. (Zainuddin et al., 2017). The success of a system being developed is determined by the critical requirements. These are the facilities that the system provides to meet the stated functionality. The online course management system should meet the students' requirements and the instructors as the core users. As discussed before that, there are two categories, functional and non-functional requirements. The functional requirements can be seen directly as discussed before, where else the non -functional requirements are satisfying constraints. This paper, therefore, aims at; Identifying the non-functional properties, the strategies for setting the non-functional properties, the contrast in the online management system to other online systems, and finally, the comparison of version control and configuration management regarding the roles and functionalities when a software system changes.

Nonfunctional properties of the system

While the functional property deals with the components that make up a system, it gives the developing team the right direction. The non-functional properties deal with the workability or the functionality of the software. This, therefore, means though varied, we must work together as a unit to ensure that the desired goals are attained. (Binkhonain & Zhao, 2019). If system requirements are compromised, it means that the project will not end successfully. Non-functional requirements tend to cover the remaining requirements from the functional requirements of a system. Criteria that guide the operation of a system are specified. For example, in the online course management system, the database should be updated every 3 seconds after data modification for all users. Non-functional requirements focus on the expectations of the user. There are several non-functional properties, and they play a series of roles towards success in learning. How fast the online course management system will respond to loading is one of the specifications. The non-functional properties are; system performance, how the system will respond throughout its utilization with time, scalability that the system can grow with the increase of users, availability, reliability, removability, security, data interoperability. These should be able to help the system performance when executed. If a student's request is made to perform a selection of courses, the process should be performed in the shortest time.

UML Diagram explaining non-functional properties of the system.

Nonfunctional Properties

Availability Requirement

Data Integrity

Reliability

Recoverability

Important in meeting the user's need when the user needs it.

Important in ensuring that there is consistency in the administration of worthwhile uncorrupted data

Important in setting a trusted system based on the number of times it can function

Important as it acts as a backup system for any damage that may occur

Testing strategy non-functional properties of the system

As already mentioned, having a management system is to keep a close follow-up on the functionality of the online learning system. (Cohen et al., 2017). Therefore, the non-functional properties have testing strategies that are employed to see to it that success is obtained. The following are some of the testing strategies often employed.

Usability Testing 

The man upon the ground or probably learner is the user. Coming along with diversity software is complex, but this doesn't mean we should stop using them. For this reason, in setting up the management system, the focus is shed upon the ease with which a user can use the system and how easy it is for the application to lead to the desired objectives.

Software load testing.

With several users simultaneously, several software systems tend to become slow in serving the given clients. Meeting a client's need at the right time is what many services always hope to archive. Similarly, a stronger system should be put into place to help serve a high number of users without interfering with other users' activity on the same site.

Failover testing 

Failover testing is a testing strategy that serves to act as an insurance policy. Just as an insurance cover takes off the worry of a customer upon an unplanned negative event, there are uncountable risks when it comes to software, but then this doesn't mean we should stop there are be ready for the negative. It, therefore, means a back-up system would be an important investment when setting up an online course management system.

Compatibility testing

Different learners have different Working platforms, which means different approaches. Therefore, there is a need to diversify the system of the service provider to be able to serve many despite their varied access systems. The more compatible a management system is, the higher the number of users it attracts and the more readily it is considered among the other online systems in the market.

The architecture for the online course management system

An architectural design is a framework that is a skeleton of a real structure itself. Architectural design is the first step of a successful online management system. It, therefore, lays down step-by-step detailed information giving more understanding to the general intended structure. However, the online course management system differs a little bit from other online systems such as Amazon or even eBay. One of the outstanding differences is the complexity in the online course management system structure, which always requires instant feedback, unlike the other systems. Apart from the above difference, its’ architecture is made open to attain compatibility with as many platforms as possible.

Version control in the development of online course management system

Software Version control involves the management of the changes that computer programs go through. Need and demand play a great role in the choosing of the right software version. Therefore, the software version sets up the management system in the right operational way that makes it acceptable to the users. There are three types of software Version Control namely; The Local Version Control System, the Centralized Version Control System, and The Distributed Version Control System. (Majumdar et al., 2017). This system offers a follow-up on the changes that occur and offers updates geared toward making the exercise much simpler and enjoyable.

The Version System is therefore of great importance and critical in the development of the management system. It ensures those guided by the same management system have uniformity in what they are gaining from the system about the advancement in the world. Following its universality and the great numbers accustomed to using the system, constant update that matches new trends is required, and storage of this transformative journey is important as it helps in knowing the blueprint from where it all starts.

List available version control software solutions

Several version control software solutions have been used. They include PerkForce, Apache Subversion, AWS Code Commit, GitHub, Microsoft Team Foundation Server, etc. Git would be a perfect Version Control Software for me because of the following reasons. It does the role of keeping a track record of the changes that occur with time. From a collaborative aspect, it develops a structure that focuses on the control software's efficiency by strengthening the Availability, Reliability, Recoverability, and Data Integrity. 

Compare and contrast version-control and configuration management.

Version control controls the tangible endpoint, while configuration management arranges the tangible endpoints to help attain the desired result. It is, therefore, true to say that the configuration management is broader and less specific while the version control is narrow and more specific. (Strasser et al. 2020). The management holds the parent role and therefore serves the foundational role in updating and adopting systems changes and ensures they are structured not to affect the delivery. The delivery in question is of the version control. Despite the difference in their roles, their working together is for the general good of establishing a successful online system.

As stated above, versions are an explanation of the broader and wider configuration management. Versions found in numerous software serve the purpose of laying down a variety of options for a single object. It also consists of several options to merge to make an application program. It is important to note that versions must be compatible to be said to have come from the same software system.

Conclusion

When developing a system, functional perspectives are the main focus that is considered. Functional requirements deal with data association, events, networks, and the business rules, while the nonfunctional give the constraints of a project. Software properties should be viewed beyond the implantation of a system. It is also essential to keep track of the changes in technology. Having version control help in identifying when necessary changes are to be made. Once the system is complete, a defined method of detecting any defects is created. This helps in delivering a quality product to the client that guarantees high performance. In conclusion, implementing nonfunctional strategies, configuration management, system testing, and establishing version control plays a major role in completing the online course management system.

References

Binkhonain, M., & Zhao, L. (2019). A review of machine learning algorithms for identification and classification of non-functional requirements. Expert Systems with Applications: X, 1, 100001.

Cohen, Y., Faccio, M., Galizia, F. G., Mora, C., & Pilati, F. (2017). Assembly system configuration through Industry 4.0 principles: the expected change in the actual paradigms. IFAC-PapersOnLine, 50(1), 14958-14963.

Majumdar, R., Jain, R., Barthwal, S., & Choudhary, C. (2017, September). Source code management using the version control system. In 2017 6th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO) (pp. 278-281). IEEE.

Strasser, T. I., de Jong, E. C., & Sosnina, M. (2020). European guide to power system testing: the ERIGrid holistic approach for evaluating complex smart grid configurations (p. 132). Springer Nature.

Zainuddin, F. B., Arshah, R. B. A., Mohamad, R. B., & Mokhtar, R. B. (2017). The human factor of formal engineering methods in validating requirement specification. Advanced Science Letters, 23(6), 5481-5486.