Software Reliability
1. (a) What are functional and non-functional requirements? (10mks)
(b) Explain the steps involved in the prototyping (10mks)
(c) Enumerate the reasons for the failure of Waterfall Model. (5mks)
2. (a) Define Software Reliability (5mks)
(b) What is Modularity? (10mks)
(c) Explain why professional software is not just the programs that are developed for a
customer. (10mks)
3. (a) What is the most important difference between generic software product development and
custom software development? What might this mean in practice for users of generic
software products? (10mks)
(b) What are the four important attributes that all professional software should have? Suggest
four other attributes that may sometimes be significant. (8mks)
(c) Apart from the challenges of heterogeneity, business and social change, and trust and
security, identify other problems and challenges that software engineering is likely to face in
the 21st century (Hint: think about the environment). (7mks)
4. (a) Based on your own knowledge of some of the application types, explain, with examples,
why different application types require specialized software engineering techniques to
support their design and development. (15mks)
(b) Explain why there are fundamental ideas of software engineering that apply to all types of
software systems. (10mks)
Sample Solution
Software Reliability Software reliability is the probability of failure-free software operation for a specified period of time in a specific environment. Software reliability is also an important factor affecting system reliability. It differs from hardware reliability in that it reflects the design perfection, rather than manufacturing perfection. Software modularity is the decomposition of a program into smaller programs with standardized interfaces. Professional software is not just the programs developed for a customer because the software is almost always packaged with associated documentation such as requirements, design models, and user manuals. A professional software goes beyond software developed solely for a customer.
tional Trademark Association (INTA) as being impracticable, for firstly, sound cannot be published by the Trademark Registry and people would have to go to the registry to hear it, and secondly, it would be difficult for the registry to store so many sound samples. But these problems seemed to have been tackled by not only the new Trade Mark Rules of 2017, but also by general technological advancements. With access to the internet and unlimited cloud storage, the INTA’s apprehensions stand redundant. The first ever sound mark to get registered was way back in 1950 when the United States Patent and Trademark Office (USPTO) recognised NBC’s infamous three chimes as a trade mark capable of being registered. Over the years, a lot of sound marks have been registered all over the world, for instance, Metro Goldwyn-Mayer’s iconic lion roar, 20th Century Fox’s chime, Tarzan’s yell, Intel’s jingle, default ring-tone of a Nokia mobile phone and many more. In India the first ever sound mark was granted to Yahoo! Inc. in 2008 for a man’s voice yodelling yahoo. ICICI Bank was the first Indian entity to obtain sound track registration with the Indian Trade Mark Registry.