wehat is requirement specification in software engineering?
91151
Telling the people writing the program exactly what you want the software to do.  NOT HOW to do it, just WHAT to do.  This should be agreed upon before the code-writing begins.  Otherwise you find yourself having to re-write lotsa code to do what the customer actually wants it to do.
347702
requirements analysis affects many of the process areas, but two specific ones that are heavily affected are requirements management (REQM) and Requirements Development (RD).  The analysis of the requirements may also be verification (VER) or validation (VAL).  For details you should check out the official book on CMMI:\n\nhttp://www.amazon.com/gp/product/0321154967/sr=8-1/qid=1144274554/ref=pd_bbs_1/103-9750914-5547864?%5Fencoding=UTF8\n\nOr take the intro to CMMI course.
692079
Surely you should know this.\n\nWhy don't you look at the course requirements and find out exactly what is needed?
610932
Systems development methodology created to radically decrease the time needed to design and implement information systems. RAD relies on extensive user involvement, Joint Application Design sessions, prototyping, integrated CASE tools, and code generators.\n\n(or)\n\nPart of a methodology that specifies incremental development with constant feedback from the customers. The point is to keep projects focused on delivering value and to keep clear and open lines of communication. Oral and written communication is not completely adequate for specification of computer systems. RAD overcomes the limitations of language by minimizing the time between concept and implementation.
235283
Send me your specifications.
968489
Selecting a Software Development Life Cycle (SDLC) Methodology: A Practical Decision Framework to Maximize Business Value (the D3 Cube)\n\nSource: Project Management Solutions\n\nDate:  May 2003\n\nPages: 12\n\n \n\n\nFREE Registration\nis required\n\n\nFormat: PDF\n\nSize: 288KB\n\nOverview: Selecting a Software Development Life Cycle (SDLC) methodology is a challenging task for many organizations. What tends to make it challenging is the fact that few organizations know what criteria to use in selecting a methodology to add value to the organization. Fewer still understand that a methodology might apply to more than one Life Cycle Model. Whether you are a Fortune 500 firm or an Armed Services agency, today's demanding time-to-market conditions have organizations focused on how to deliver the needed solutions faster. Business budget, time, and functionality requirements are driving business value and defining market changes.\n\nTopics:  Methodology, Software Engineering\n\nTags:  project management, software development, software, Project Management Solutions Inc.\n\n(Is this item miscategorized? Does it need more tags? Let us know.)\n\n\n \n\nPeople who downloaded this item also downloaded\nWhite Paper Integrating Human-Computer Interaction Development Into SDLC: A Methodology Syracuse University August 2004\nWhite Paper Managing Requirements Changes in SDLC Borland Software September 2004\nWhite Paper Project Management Methodologies AEW Services July 2005\nWhite Paper The Development Process Made Easy Goda Software July 2005\n \n\nTop results from Methodology\n\nFree Member Benefit\nWhite Paper Forrester Report: The Changing Face of Application Lifecycle Management SERENA Software August 2006\nWhite Paper IDC Executive Brief: Driving Enterprise Change Management for Business Responsiveness SERENA Software May 2006\nResearch Report Taking Your PMO to the Next Step: The Office of the CIO Forrester Research September 2005\nWhite Paper Requirements Management: The Proven Way to Accelerate Development SERENA Software May 2005\nWhite Paper Offshore Software Test Automation: A Strategic Approach to Cost and Speed Effectiveness LogiGear \n\n\nvisit here\nhttp://whitepapers.techrepublic.com.com/whitepaper.aspx?&kw=SDLC&docid=158378
175766
the term "user requirements" deal mainly with any "software design".\nit is the first stage in software development where you go to the user & ask what are his requirements in the software.\ne.g->"look & feel" of the software.\nin this stage,we design a document called\n"SRS"(software requirements & specifications).\nthis is the most required document at every stage of "software development".\n\nfor more details,refer to the book,\nsoftware engineering by K.K.Aggarwal
500493
requirements gathering - the exact requirements\nanalysis - requirement specification\ndesign - design specification\nimplementation - prototype\ntesting - modified prototype\nmaintenance
334575
Software engineering:  \nThe computer science discipline concerned with developing large applications. Software engineering covers not only the technical aspects of building software systems, but also management issues, such as directing programming teams, scheduling, and budgeting. \n \nUsability engineering:\nA subset of human factors that is specific to computer science and is concerned with the question of how to design software that is easy to use. It is closely related to the field of human-computer interaction and industrial design.
137108
DEFINITION: System Development Life Cycle (SDLC) is the overall process of developing information systems through a multistep process from investigation of initial requirements through analysis, design, implementation and maintenance. There are many different models and methodologies, but each generally consists of a series of defined steps or stages. \n\n\nMAY 14, 2002 (COMPUTERWORLD) - Once upon a time, software development consisted of a programmer writing code to solve a problem or automate a procedure. Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of custom-written code that drive our enterprises. \nTo manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize. \n\nThe oldest of these, and the best known, is the waterfall: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following: \n\n\n\nProject planning, feasibility study: Establishes a high-level view of the intended project and determines its goals. \n\nSystems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs. \n\nSystems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation. \n\nImplementation: The real code is written here. \n\nIntegration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. \n\nAcceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business. \n\nMaintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.\n\nBut It Doesn't Work! \n\nThe waterfall model is well understood, but it's not as useful as it once was. In a 1991 Information Center Quarterly article, Larry Runge says that SDLC "works very well when we are automating the activities of clerks and accountants. It doesn't work nearly as well, if at all, when building systems for knowledge workers -- people at help desks, experts trying to solve problems, or executives trying to lead their company into the Fortune 100."  \nAnother problem is that the waterfall model assumes that the only role for users is in specifying requirements, and that all requirements can be specified in advance. Unfortunately, requirements grow and change throughout the process and beyond, calling for considerable feedback and iterative consultation. Thus many other SDLC models have been developed. \n\nThe fountain model recognizes that although some activities can't start before others -- such as you need a design before you can start coding -- there's a considerable overlap of activities throughout the development cycle. \n\nThe spiral model emphasizes the need to go back and reiterate earlier stages a number of times as the project progresses. It's actually a series of short waterfall cycles, each producing an early prototype representing a part of the entire project. This approach helps demonstrate a proof of concept early in the cycle, and it more accurately reflects the disorderly, even chaotic evolution of technology. \n\nBuild and fix is the crudest of the methods. Write some code, then keep modifying it until the customer is happy. Without planning, this is very open-ended and can by risky. \n\nIn the rapid prototyping (sometimes called rapid application development) model,
929262
Information Technology Engineering is more commonly called Software Engineering (SE).\n\nSoftware Engineering is the design, development, and documentation of software by applying technologies and practices from computer science, project management, engineering, application domains, interface design, digital asset management and other fields.\n\nPlease see the Wikipedia article below.
633705
Here is a complete definition with details...Too much info to type it all in here...\nhttp://en.wikipedia.org/wiki/Software_development
1016509
Software Engineering !!!
1159557
The book that I have and like:\n\nUML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition, by Martin Fowler\n\nIt tells you just what you need, with a view toward using the UML diagrams in realistic scenarios.  It is not overly academic and it concentrates on the diagrams that real programmers use most.
580145
Requirements gathering, coding, testing, documentation of IT solutions based on Oracle's Applications or technology
435278
IEEE 829 - Test Procedure Specification (TPS)\n\n\n...did you SEE the memo about the new cover sheet?
13560
There really isn't any difference in describing what you need to a web developer or a software developer. They will both be looking for (if they are worth describing the problem to) in no particular order:\n1. context diagrams that define how the external interfaces interact with your system,\n2. what the requirements (functional, non-functional, constraints) of the system,\n3. a flow chart describing how the user interacts with your front-end,\n4. how you want the data to be stored,\n5. a set of well defined business rules have always helped me,\n6. describe what your vision of the application is, the goals and what you hope to accomplish in the future with it (this will help the developer make strong decisions may affect any future modifications and extensibility of the application).\n\nMy best recommendation to you is to just lay everything and anything you can think of down on the table. Obviously, do it after you've deemed them worthy of the job.