|
Requirements Elicitation
In requirements engineering, requirements elicitation is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders. The practice is also sometimes referred to as "requirement gathering". The term elicitation is used in books and research to raise the fact that good requirements cannot just be collected from the customer, as would be indicated by the name requirements gathering. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user and customer by just asking them what the system should do or not do (for Safety and Reliability). Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brainstorming, use cases, role playing and prototyping. Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. Requirements elicitation is a part of the requirements engineering process, us ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Requirements Engineering
Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term ''requirements engineering'' was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference. In the waterfall model, requirements engineering is presented as the first phase of the development process. Later development methods, including the Rational Unified Process (RUP) for software, assume that requirements engineering continues through a system's lifetime. Requirement management, which is a sub-function of Systems Engine ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Non-functional Requirement
In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing ''functional'' requirements is detailed in the system ''design''. The plan for implementing ''non-functional'' requirements is detailed in the system ''architecture'', because they are usually architecturally significant requirements. Definition Broadly, functional requirements define what a system is supposed to ''do'' and non-functional requirements define how a system is supposed to ''be''. Functional requirements are usually in the form of "system shall do ", an individual action or part of the system, perhaps explicitly in the sense of a mathematical function, a black box description input, output, process and control functional model or ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Murali Chemuturi
Murali Krishna Chemuturi (popularly known as Murali Chemuturi) (born 28 June 1950) is an Indian software development expert. He authored ten books, six on software development management, one on management, two translations (Ramayana, and Bhagavad Gita from Sanskrit into English) and one on personality engineering. He has also published a number of papers in journals and on the Internet. Life and work Born in Chityala, State of Andhra Pradesh, India to father Appa Rao Chemuturi and mother Chintapenta Vijaya Lakshmi, Murali Chemuturi studied Electrical Engineering at SMVM Polytechnic, Tanuku, followed by Industrial Engineering from Indian Institution of Industrial Engineering and PG Diploma in Computer Methods and Programming from AP Productivity Council. He finished academics with MBA from the College of Commerce and Business Management of Osmania University Hyderabad. He started working at Electronics Corporation of India Limited, Tata Consultancy Services, Metamor Global So ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Prototyping
Software prototyping is the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed. It is an activity that can occur in software development and is comparable to prototyping as known from other fields, such as mechanical engineering or manufacturing. A prototype typically simulates only a few aspects of, and may be completely different from, the final product. Prototyping has several benefits: the software designer and implementer can get valuable feedback from the users early in the project. The client and the contractor can compare if the software made matches the software specification, according to which the software program is built. It also allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and milestones proposed can be successfully met. The degree of completeness and the techniques used in prototyping have been in development and debate ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Electronic Meeting System
An electronic meeting system (EMS) is a type of computer software that facilitates creative problem solving and decision-making of groups within or across organizations. The term was coined by Alan R. Dennis et al. in 1988. The term is synonymous with group support systems (GSS) and essentially synonymous with group decision support systems (GDSS). Electronic meeting systems form a class of applications for computer supported cooperative work. Mainly through (optional) anonymization and parallelization of input, electronic meeting systems overcome many deleterious and inhibitive features of group work. Similar to a web conference, a host invites the participants to an electronic meeting via email. After logging into the session, meeting attendees participate primarily through their keyboards, typing responses to questions and prompts from the meeting host. Delineation Electronic meeting systems need to be distinguished on the one hand from classic groupware, on the other from w ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Interview
An interview is a structured conversation where one participant asks questions, and the other provides answers.Merriam Webster DictionaryInterview Dictionary definition, Retrieved February 16, 2016 In common parlance, the word "interview" refers to a one-on-one conversation between an ''interviewer'' and an ''interviewee''. The interviewer asks questions to which the interviewee responds, usually providing information. That information may be used or provided to other audiences immediately or later. This feature is common to many types of interviews – a job interview or interview with a witness to an event may have no other audience present at the time, but the answers will be later provided to others in the employment or investigative process. An interview may also transfer information in both directions. Interviews usually take place face-to-face and in person but the parties may instead be separated geographically, as in videoconferencing or telephone interviews. I ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Requirement Prioritization
Requirement prioritization is used in the Software product management for determining which candidate requirements of a software product should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first. Several methods for assessing a prioritization of software requirements exist. Introduction In Software product management there exist several sub processes. First of all there is portfolio management where a product development strategy is defined based on information from the market and partner companies. In product roadmapping (or technology roadmapping), themes and core assets of products in the portfolio are identified and roadmap constructions are created. In requirements management candidate software requirements for a product are gathered and organized. Finally, in the release planning activity, these requirements are prioritized and selected for a release, ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Design Rationale
A design rationale is an explicit documentation of the reasons behind decisions made when designing a system or artifact. As initially developed by W.R. Kunz and Horst Rittel, design rationale seeks to provide argumentation-based structure to the political, collaborative process of addressing wicked problems. Overview A design rationale is the explicit listing of decisions made during a design process, and the reasons why those decisions were made.Jarczyk, Alex P.; Löffler, Peter; Shipman III, Frank M. (1992), "Design Rationale for Software Engineering: A Survey", ''25th Hawaii International Conference on System Sciences'', 2, pp. 577-586 Its primary goal is to support designers by providing a means to record and communicate the argumentation and reasoning behind the design process.Horner, J.; Atwood, M.E. (2006), "Effective Design Rationale: Understanding the Barriers", in Dutoit, A.H.; McCall, R.; Mistrík, I. et al., Rationale Management in Software Engineering, Spr ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Use Case
In software and systems engineering, the phrase use case is a polyseme with two senses: # A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful. # A potential scenario in which a system receives an external request (such as user input) and responds to it. This article discusses the latter sense. A ''use case'' is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an ''actor'') and a system to achieve a goal. The actor can be a human or another external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements. History In 1987, Ivar Jacobson presented the first article on use cases at the OOPSLA'87 conference. ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Brainstorming
Brainstorming is a group creativity technique by which efforts are made to find a conclusion for a specific problem by gathering a list of ideas spontaneously contributed by its members. In other words, brainstorming is a situation where a group of people meet to generate new ideas and solutions around a specific domain of interest by removing inhibitions. People are able to think more freely and they suggest as many spontaneous new ideas as possible. All the ideas are noted down without criticism and after the brainstorming session the ideas are evaluated. The term was popularized by Alex Faickney Osborn in the classic work ''Applied Imagination'' (1953). History In 1939, advertising executive Alex F. Osborn began developing methods for creative problem-solving. He was frustrated by employees' inability to develop creative ideas individually for ad campaigns. In response, he began hosting group-thinking sessions and discovered a significant improvement in the quality and qua ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Scenario (computing)
In computing, a scenario (, ; loaned (), ) is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software. A scenario has a goal, which is usually functional. A scenario describes one way that a system is used, or is envisaged to be used, in the context of an activity in a defined time-frame. The time-frame for a scenario could be (for example) a single transaction; a business operation; a day or other period; or the whole operational life of a system. Similarly the scope of a scenario could be (for example) a single system or a piece of equipment; an equipped team or a department; or an entire organization. Scenarios are frequently used as part of the system development process. They are typically produced by usability or marketing specialists, often working in concert with end users and developers. Scenarios are written in plain language, with min ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Context Analysis
Context analysis is a method to analyze the environment in which a business operates. Environmental scanning mainly focuses on the macro environment of a business. But context analysis considers the entire environment of a business, its internal and external environment. This is an important aspect of business planning. One kind of context analysis, called SWOT analysis, allows the business to gain an insight into their strengths and weaknesses and also the opportunities and threats posed by the market within which they operate. The main goal of a context analysis, SWOT or otherwise, is to analyze the environment in order to develop a strategic plan of action for the business. Context analysis also refers to a method of sociological analysis associated with Scheflen (1963) which believes that 'a given act, be it a glance at notherperson, a shift in posture, or a remark about the weather, has no intrinsic meaning. Such acts can only be understood when taken in relation to one another. ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
.jpg "Click for more on -> Interview")
.jpg "Click for more on -> Brainstorming")