My Program Manager has asked me to help the System Engineers perform a bunch of

Question

My Program Manager has asked me to help the System Engineers perform a bunch of analyses to support future assessments and decision-making regarding our SOI. When I shrugged with confusion, she offered me "a hint" by saying I could start with the "ilities." I thought she was kidding! Now I'm hearing from the SE that ilities are some kind of big deal. Who knew?

I need two paragraphs that I can use to generate a couple of slides to brief the PM. Please describe how I'm going to figure out which ilities matter and why. Thanks in advance for your help.

The Intern

Explanation / Answer

Non-functional requirements are often called "quality attributes" of a system.In informal sense; Non functional requirements are called ilities. In other words within systems engineering, quality attributes are realized non-functional requirements used to evaluate the performance of a system. In the world of software architecture there are many “-ilities” we must take into consideration with every project and Prioritizing them is very important.

Qualities—that is non-functional requirements—can be divided into two main categories:

1. Execution qualities, such as safety, security and usability, which are observable during operation (at run time).

2. Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the system.

Related Questions

Navigate

• Browse (All)
• Browse M
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.