Software Development Life Cycle Essay

Pages: 12 (3695 words)  ·  Bibliography Sources: ≈ 28  ·  File: .docx  ·  Level: Master's  ·  Topic: Business - Management

SAMPLE EXCERPT . . .
One is the organizational approach that has better success rate. In other words the system creation and management is very important. There have been vast changes in the very functions of government and these changes have been made in many sectors that are the core of the government, the "nodality, authority, treasure and organization." (Margetts, 1999) These thus are vital concepts that actually take in the system development from the side of the client and the developer.

Question 3. As part of design process in SDLC, what quality attributes should be focused on? Describe each in detail.

Quality is the key in the software development necessary at many levels: Primarily the changes that occur in the hardware and the software industry the programmers have to be also upgraded to keep the quality of programming. They must also be able to get "new knowledge and skills; and must thus acquire a variety of knowledge bases" and are the victims of increasing work intensity seem to make the work tedious with attrition. (Docherty; Forslin; Shani, 2002)

Thus loss of key personnel has a major impact on the quality. However the general method of improvement still functions well. The method of process improvement simply is the selection of the paradigms that work and elimination of those which were problematic in the past. The first step to this is to begin by correcting the problems that were seen in the systems in the past. If the system as of now works well the need to change it must be considered with caution and the impact the changes will have on the users. The second necessity is anticipating problems that may be created in the future. (Wiegers, 2012)Get full Download Microsoft Word File access
for only $8.97.

Essay on Software Development Life Cycle ( Assignment

The aim of development however is to see that the system is "intelligent" and "autonomous" in response and minimize the tasks for the user. The opposite end is to see that the human problem solving potential is exploited and leaves the system as the executor of the solution where the user designs the responses in the system to the needs. (Oppermann, 1994) The major consideration is on quality focus on the infrastructure that would be needed for the project. Thus there must be quality infrastructure available and along with that there be a method of measuring the process. The process measurement is based on many quantitative techniques that are used to diagnose software processes and find information on quality and the weakness and strengths. It is also used for the process implementation and for evaluation. (Emam, 2001)

The definitions of the process also decide the quality. Thus models have to be created that can elucidate the processes and the tasks and paradigms involved. These steps make it possible for the life cycle processes to be fit to any life cycle frameworks. The two important quality determining procedures are the "ISO/IEC 12207: Information Technology -- Software Life Cycle Processes [80] and ISO/IEC TR 15504: and the Information Technology -- Software Process Assessment [42][81]. Both being produced by the IEEE and they consist of the definitions of the measurement scale to evaluate the capability of the processes." (Emam, 2001)

Thus by adhering to the IEEE standard on developing life cycle processes the quality can be set and maintained for the system lifecycle and the maintenance processes and for creating quality software. The system is important to the management of inventory and all other functions order taking, logistics, delivery and stocking merchandise. Order processing has many vital divisions that have to be understood in the individual context and the system as a whole. Even in a small operation the information system ought to have better tracking functions, "data analysis and reporting, vendor management, customer databases processing and marketing analysis feasibility." (Lagana, 2004) Only when such an integrated system is developed tailor made to the business, can the efficiency required to be competitive be perceived in the business. (Lagana, 2004)

The technology driven market has brought in the way of complex ordering processes for example the traditional mail order is replaced with e-commerce. Thus online and store front services have merged and this require customized configuration, with the inclusion of the possible services. The success of the business could thus depend upon the proper implementation of proper systems that could adapt to complex ordering processes. The most important is the management of customer orders which could then affect the profitability or viability of a company. The creation of a system undergoes many stages, with the definition of the business strategy, and the mission and needs of the organization, which is then analyzed as to its functioning model which can be called the environment of business and the way the work is to be accomplished and the transactions involved. (Lagana, 2004)

This lays the foundation for the security analysis and the design of the system. In any system the need for computer system security is present but it is more marked in the case where a network environment is a part of the system. This opens up a possibility of unauthorized entry, or where there is sensitive data that is not to be disclosed and the vulnerability of the system persists. There are many criteria with which individual institutions may define security. It may be the integrity factor, where the primary concern is protecting the interest defined either in terms of integrity, privacy or the safety of transactions. In modern times all three are relevant and are probably basic requirements. The fact that persistent intruders could access at any time the systems and play havoc prompted the trial of many security systems within the IT system of the organizations.

Question 4. Explain the Design principles for System Development Life Cycle

Software development life cycle is a conceptual model used in project management that describes the stages involved in an information system development. It is the methodologies which people use to develop systems of software development in a continuous process called the life cycle. It is the most important concept in software development and it is vital to the implementing organization for mapping out and planning how to implement the software development life cycle. Software development life cycle should be client oriented and a generic overview concerning completely different client oriented software development methodologies. The software development life cycle has numerous activities and steps, some simultaneous and some sequential. These steps, including validating the system, requirement analysis and finally the testing of software has all the process mapped out in a formal set of documents and the logical steps that must be taken to develop a software product are part of the cycle. However the vast changes in the world have made some of these processes out dated. The basic paradigm of development is now old. (Kliem; Ludin, 1994)

It is contended that development methods must change with the demands of the developing technology. Some of the methods of systems development have now become obsolete. The case is that in the older systems development paradigm there is a central goal -- the creation of a viable product as fast as it can be created. The process of arriving at the product is not material. The developers work in this system with the end in sight rather than the robustness of what they create. These developers are thus a "good case of tunnel vision" and this approach is called the "archaic paradigm." (Kliem; Ludin, 1994) This method has its own steps and that begins with the analysis and design, after which there comes construction, followed by implementation, and finally management. The methods may vary and be different, but in short, the System Development Life Cycle -- SDLC is a method that is used to ensure that the final software is perfect and meets the requirement that it is created to fulfill. (Kliem; Ludin, 1994)

To arrest the waywardness and different perceptions of developers the life cycle is a system that brings in quite a lot of work ethos and f discipline to the software development process thereby making the process highly specialized and very efficient. Merely because it is some what old does not mean that it has no value. There is still the strength in the traditional method although the modern methods are faster and with out so many processes. Both have to be considered simultaneously with highlights on the differences between them. The traditional SDLC methodologies sometimes fall short in the new e-business software environment and cannot keep up with the pace of e-business software development projects. Hence now "light" SDLC methodologies with reduced documentation and managerial effort are now being used. (Wolak, 2001)

Traditional software development models used the code and fix, waterfall, "staged and phased development, transformational, spiral, and iterative models." (Wolak, 2001) In the traditional method the aim was to create the state of the art software systems that always met customer expectations, used up only the available resources and infrastructure, and was not very costly. Thus the process begins with the defining of the requirements, and… [END OF PREVIEW] . . . READ MORE

Two Ordering Options:

?
Which Option Should I Choose?
1.  Buy full paper (12 pages)Download Microsoft Word File

Download the perfectly formatted MS Word file!

- or -

2.  Write a NEW paper for me!✍🏻

We'll follow your exact instructions!
Chat with the writer 24/7.

Project Life Cycle and Product System Term Paper


Product Project Life Cycles Term Paper


Company, Stellar Systems Consulting Is Helping Dave Term Paper


Product Life Cycle of SAP Essay


Product Life Cycle Norton Antivirus Software Research Paper


View 200+ other related papers  >>

How to Cite "Software Development Life Cycle" Essay in a Bibliography:

APA Style

Software Development Life Cycle.  (2012, April 19).  Retrieved March 7, 2021, from https://www.essaytown.com/subjects/paper/software-development-life-cycle/8596235

MLA Format

"Software Development Life Cycle."  19 April 2012.  Web.  7 March 2021. <https://www.essaytown.com/subjects/paper/software-development-life-cycle/8596235>.

Chicago Style

"Software Development Life Cycle."  Essaytown.com.  April 19, 2012.  Accessed March 7, 2021.
https://www.essaytown.com/subjects/paper/software-development-life-cycle/8596235.