a)Object Points and Function Points are general, high level system size metrics. Which aspects of the software system are taken into account in the Object Point metric, and which in the Function Point metric? b) ISO standards define a set of software quality characteristics and sub-characteristics. They specify which quality characteristics are influenced by which sub-characteristics. i. Discuss briefly quality sub-characteristics affecting software reliability and software usability. ii. Explain why highly reliable systems tend to be less efficient.

a)Object Points and Function Points are general, high level system size metrics. Which aspects of the software system are taken into account in the Object Point metric, and which in the Function Point metric? b) ISO standards define a set of software quality characteristics and sub-characteristics. They specify which quality characteristics are influenced by which sub-characteristics. i. Discuss briefly quality sub-characteristics affecting software reliability and software usability. ii. Explain why highly reliable systems tend to be less efficient.

Fundamentals of Information Systems

9th Edition

ISBN:9781337097536

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter8: System Acquisition And Development

Section: Chapter Questions

Problem 3.2CTQ: A safety-critical system is one whose failure or misuse may cause human injury or death. Given that...

See similar textbooks

Similar questions

a) Reliability and Usability are important software quality attributes. Give a brief explanation of both attributes and discuss which of these attributes is easier to quantify and measure. b) Object Points and Function Points are general, high level system size metrics. Which aspects of the software system are taken into account in the Object Point metric, and which in the Function Point metric?
a) With respect to Lehman's laws of software evolution, state the two most fundamental laws and explain their implication for software lifecycle management. b) When you are assessing a legacy system, you have to look at it from a business perspective and a technical perspective. From a business perspective, you have to decide whether the business really needs the system. From a technical perspective, you have to assess the quality of the system and its related support software and hardware. You then use a combination of the business value and the system quality to take one of the following informed decisions: scrap the system, re- engineer the system, replace the system, continue the system's maintenance. Your task is to assess legacy systems in your organization and decide what would be the most appropriate strategy for maintaining these systems. i, Discuss possible factors you would use when assessing the technical quality of the legacy system. ii. Assume that you assessed four…
a) Reliability and Usability are important software quality attributes. Give a brief explanation ofboth attributes and discuss which of these attributes is easier to quantify and measure.b) Object Points and Function Points are general, high level system size metrics. Which aspectsof the software system are taken into account in the Object Point metric, and which in theFunction Point metric?c) ISO standards define a set of software quality characteristics and sub-characteristics. Theyspecify which quality characteristics are influenced by which sub-characteristics.i. Discuss briefly quality sub-characteristics affecting software reliability and softwareusability.ii. Explain why highly reliable systems tend to be less efficient.
a.In the context of software architecture, what are business goals? b.How should they influence software architecture? c. What is a Business Scenario? How do these scenarios aid software architecture design?
1. Scalability is one of the quality attributes of a software system. Explain five tactics of scalability of the hospital information system. You should provide a detailed critical analysis of your tactics relevant to the hospital information system. [Note: you can formulate your own tactics] 2. With reference to Question 1, identify an architectural pattern which can suit the operation of the hospital. You are expected to write about the identified architectural pattern in the context of the hospital information system. You shall write only ONE architectural pattern. Ideally, the architectural pattern should be compatible with the tactics explained in Question 1.
It is important during software design to reduce coupling and increase cohesion where possible. a) Give TWO (2) possible complications that may arise if two modules have high coupling. b) Explain how common coupling occurs. c) Explain how the concepts of coupling and cohesion are related to software module size.
The influence of cohesion and coupling on software development and maintenance is a topic of significant academic interest. Cohesion refers to the degree to which the components of a software system are logically related and work together to achieve a common goal. High cohesion is desirable as it promotes modularization, reusability, and ease of understanding and modification. On the other hand, coupling refers to the interdependencies between software components. Low
When discussing software architecture, what is the relationship between the ideas of cohesiveness and coupling?
Software architecturechoose the correct answer Reflect the behavior of the system during its execution: a. Static Quality Attributes b. runtime behavior Attributes c. Dynamic Quality Attributes d. Quality Attributes
It is clear that a software development project carried out by a software house for a specific customer is carried out under content and timetable obligations, and is subject to the customer-supplier relationship. 1. Discuss whether a customer-supplier relationship is expected when the software developed is to be sold to the public as a software package. 2. Discuss whether a customer-supplier relationship is expected when software is developed for "in-house" use, as in the case where a software development department develops an inventory program for the company's warehouses. 3. Some managers claim that the closer relationships are to a formal pattern, the greater the prospects are for the project's success. Discuss whether implementing customer- supplier relationships in the situations mentioned in (1) and (2) are a benefit for the company (referring to the internal customer and supplier) or an unnecessary burden to the development team.
Every job and every professional path carries with it a certain amount of power. In addition, having power brings a certain degree of responsibility proportional to that authority. What skills do you feel a software engineer acquires just by virtue of the fact that they work in this industry? Keeping in mind the IEEE code of Ethics for Software Engineering, what do you believe are the capabilities that accrue to a software engineer because they work in this field?
Explain the concept of a formal system model in software engineering. How can formal methods be applied to verify software correctness and reliability?