2. What is the most crucial difference between generic software product custom and development software development? What might this mean used for users of generic software products? What is the most important difference between universal software product development and custom software development? Custom software development these are systems that are commissioned by a particular customer. A software service provider builds up the program for that customer especially. Generic software product development these are stand-alone systems that are produced by a development organization and sold on the open market to any customer who’s able to get them. Examples of this type of product include software for PCs such as directories, word processors, sketching deals, and project-management tools.
The difference is that in a generic software product development, the standards are possessed by the product builder. For custom product development, the specification is owned and controlled by the client. Generic software has no specific target in mind, and development comes after that basic idea. It really is designed from its conception to include every function they could possibly use, and be accessible in a manner that will not leave the user feeling that the program is “bloated” or overrun with useless features.
Custom software, on the other hand, is conceptualized by the customer it is developed for, and development and creation are guided by the client. What might this mean used for users of generic software products? For users of universal products, this implies they have no control over the program standards so cannot control the evolution of the product.
The developer may decide to include/exclude features and change the user interface. This may have implications for the user’s business procedures and add extra training costs when new versions of the machine are installed. In addition, it may limit the customer’s versatility to change their own business procedures. However, the difference between these system product types is becoming blurred increasingly. 3. What are the four important features that good/professional software must have? Suggest four other qualities that may sometimes be significant.
What are the four important attributes that good/professional software must have? Maintainability: Software designer must develop software that can be easily scalable to meet up with the changes in the business environment and their customers’ needs as they arise. Dependability and security: software should be reliable and well crafted to ensure safe data writing among users, and business as well as protect the integrity of the machine and an individual alike. Acceptability: The Software should be easily usable, understandable, and compatible with other systems that it might be used on. Inter-operability -Ability to work with an array of other software systems.
4. Identify problems and problems that software engineering is likely to face in the 21st century (hint: think about the environment). There are several possible challenges that could be identified. Developing systems that are energy-efficient. This makes them more usable on low-power cellular devices and helps decrease the overall carbon footprint from it equipment.
Developing validation techniques for simulation systems (which will be essential in predicting the level and planning climate change). Costs and regularity of change. Some systems (such as embedded systems in consumer devices) are extremely expensive to improve; others must change frequently in response to varying requirements (e.g. Business systems).
- 1-10-2011 Dr. Cash A/c………………………Rs.7,20,000
- The best architectures, requirements, and designs emerge from self-organizing teams
- Health administration (MS, MHA)
- Include a graphic, and make sure the image contains less than 20% text message
- Blockchain technology to bolster fintech
Systems which are very expensive to improve need extensive in advance evaluation to ensure that certain requirements are constant and intensive validation to ensure that the machine meets its standards. The most important ‘non-functional’ requirements. Different systems have different priorities for non-functional requirements. For instance, a real-time control system in an aircraft has safety as its primary priority; an interactive game has usability and responsiveness as its concern. The techniques used to achieve safety aren’t required for interactive gaming; the intensive UI design necessary for games is not needed in safety-critical control systems. The software delivery and lifetime schedule.
Some software systems have a comparatively short life time (many web-based systems), others have a lifetime of tens of years (large order and control systems). Some systems need to be shipped if they’re to be useful quickly. The techniques used to build up short-lifetime, rapid delivery systems (e.g. use of scripting dialects, prototyping, etc.) are unacceptable for long-lifetime systems which require techniques that allow for long-term support such as design modeling. Software specification where customers and designers define the program that is to be produced and the constraints on its procedure. Software development, where the software is programmed and designed. They should be developed using an understood and managed development process.