Sign Up Now
Get instant access to over 1 million+ study documents
OR
Already registered? click here to login
By creating your account, you agree to our terms of service, privacy policy and student honor code.
¶ … poor requirements for development software vs. The problems that occur from poor requirements management
A good manager will present his or her staff with clearly defined requirements, realistic schedules, ask for a product whose specifications can be subject to adequate testing, present his or her staff with reasonable but firm specifications, and have good communication skills. A poor manager will do just the opposite -- not only will he or she have poor interpersonal skills, but quite often a bad manager will present vague specifications for the developing software that workers cannot easily test, and simply demand too much, too quickly, on too tight a budget or a schedule of the staff. (Davis, 2004)
Poor management can of course contribute to some of the different kinds of failures in requirements for development software. For example, a rushed schedule can result, on the part of the software developers, with key user requirements being dropped from the product. This can create a faulty, bug-ridden, and confusing system for the customer's employees. (Chin, 2003) Thus, the managerial, people-related failure of a cramped schedule creates a failure on the software staff to meet specific and reasonable technical requirements of the customer. A lack of clear and testable managerial requirements can also lead to interpersonal conflicts amongst software staff regarding product methodology of design, creating an overly confusing architecture. Conversely, systems may be overly simplified to accommodate a tight schedule, resulting in a susceptibility to viruses and worms. (Chin, 2003)
Thus, the problems relating to poor management are those of scheduling, setting defined limits and product quality controls, and relating to people. The problems with software design development usually revolve around meeting customer needs and specifications on a technical level. But both problems must be solved for a workplace to function at its maximum level of efficiency.
Works cited
Chin, Paul. (May 6, 2003) "Cold Case: Project Failure." CIO Online. Retrieved 13 Jan 2005 at http://www.itmanagement.earthweb.com/cio/article.php/2201981
Davis, Rob. (2004) "Five Common Problems that occur during software development." Software Testing Engineer. Retrieved 13 Jan 2004 at http://www.robdavispe.com/free2/software-qa-testing-test-tester-2011.html
software processes of sometime deteriorate into non-Productive arguments. Why does this occur? If only human being's egos could be as carefully streamlined of nonproductive processes as the software applications they design, the workplace would be a far more productive space. The reasons for non-productive arguments are often rooted in the same sources as other workplace and even family conflicts. Clashes of personal ego create arguments that have little to do
Software Development Life Cycle Agile Software Development Agile software development is a popular software development process or methodology that has gained a lot of popularity in the recent years due to its effectiveness and ease of use. Firstly, it encourages collaboration and teamwork throughout the life cycle of development and this makes it easy to plan and implement. Agile software development is all about breaking a task into small chunks that make it
Software Development Life Cycle ( SDLC) Explain Requirement process ( in SDLC) in detail. Why is this exercise important? Requirements engineering is a fundamental activity in systems development and it is the process by which the requirements for software systems are identified, systematized and implemented and are followed through the complete lifecycle. Traditionally engineers focused on narrow functional requirements. Now it is being argued by Aurum and Wohlin (2005) that focusing only
Software Testing Strategy Computers and their applications have brought about waves of changes in various areas of science and technology. It is also gaining widespread prominence in the field of business and management. So the requirement of a quality oriented technological implementation, having a range of usage is the order of the day. The few gazillion dollars worth software industry is constantly evolving with the needs of people and organizations across
Software Processing Methodology Understanding the Problem Klyne Smith, DSE Candidate Dr. Frank Coyle Technical Motivation Research and Contribution Methods Software Processing Methodologies Waterfall Methodology Strengths Weaknesses Opportunity Threats Iterative Methodology Strengths Weaknesses Opportunities Threats Model Methodology Strengths Weaknesses Opportunities Threats Where do we go from here (Spring 2010)? Define measurement data points for Test Case analysis Section IV Creation and Validation of the predictive model Section V Summary Analysis Practical Usage Praxis Conclusion Books Articles / Web Information Software Processing Methodology: Understanding the Problem Section I: Introduction In this work, I examine three different Software Processing Methodologies. I start with the iterative model, followed by the spiral
Management Requirements engineering process is at the very core of project success. Rather than spend huge amounts of money for reworking the whole project it is prudent and cost effective to identify and rectify the problems early in the project development life cycle. We are witnessing a paradigm shift in communication and computer technology and there is a consequent change in our business methodologies. In this automated business environment there is