Find link

language:

Find link is a tool written by Edward Betts.

searching for Requirements analysis 73 found (150 total)

Systems analysis (801 words) [view diff] exact match in snippet view article find links to article

their purpose. The field of system analysis relates closely to requirements analysis or to operations research. It is also "an explicit formal inquiry

Application security (1,094 words) [view diff] exact match in snippet view article find links to article

applications. It encompasses the whole application life cycle from requirements analysis, design, implementation, verification as well as maintenance. Web

IEC 62304 (396 words) [view diff] exact match in snippet view article find links to article

Software safety classification Software development planning Software requirements analysis Software architectural design Software detailed design Software

Requirements elicitation (1,204 words) [view diff] no match in snippet view article find links to article

dependencies. Documenting dependencies and interrelationships among requirements. Analysis of changes. Performing root cause analysis of changes to requirements

Accounting information system (2,604 words) [view diff] case mismatch in snippet view article find links to article

implement an accounting information system are as follows: Detailed Requirements Analysis where all individuals involved in the system are interviewed. The

Implementation (723 words) [view diff] exact match in snippet view article find links to article

use of the software or hardware that was purchased. This includes requirements analysis, scope analysis, customizations, systems integrations, user policies

Software assurance (3,035 words) [view diff] exact match in snippet view article find links to article

software products. It involves a variety of activities, including requirements analysis, design reviews, code inspections, testing, and formal verification

Enterprise unified process (442 words) [view diff] case mismatch in snippet view article find links to article

Unified Process defines nine project disciplines Business Modeling Requirements Analysis and Design Implementation Test Deployment Configuration and Change

Use case diagram (436 words) [view diff] exact match in snippet view article find links to article

(October 7, 2004). "Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML". Requirements

Factory Instrumentation Protocol (373 words) [view diff] exact match in snippet view article find links to article

FIP standard is based on a French initiative in 1982 to create a requirements analysis for a future field bus standard. The study led to the European Eureka

IDEF4 (1,923 words) [view diff] exact match in snippet view article find links to article

designed to support smooth transition from the application domain and requirements analysis models to the design and to actual source code generation. It specifies

Grady Booch (1,262 words) [view diff] case mismatch in snippet view article find links to article

following activities cycle: Conceptualization : establish core requirements Analysis : develop a model of the desired behavior Design : create an architecture

GTRI Information and Communications Laboratory (270 words) [view diff] exact match in snippet view article find links to article

development. ICL also provides C4I capabilities and functional requirements analysis to various service components across the Department of Defense in

Functional requirement (677 words) [view diff] case mismatch in snippet view article find links to article

ISBN 9781351831420. Retrieved 15 June 2018. "Supplement 4-A, A Procedure for Requirements Analysis". Systems Engineering Fundamentals (PDF). United States Government

Land Information and Communications Services Group (292 words) [view diff] exact match in snippet view article find links to article

functions which it can undertake include: Strategic, operational and requirements analysis Planning Solution design Programme and project implementation In-service

Construction by configuration (197 words) [view diff] exact match in snippet view article find links to article

avoid the mostly failures reported. These are: System selection. Requirements analysis. Business process redesign. System configuration. System testing

Organizational patterns (1,726 words) [view diff] no match in snippet view article find links to article

Montenegro, November 15, 2004, pp. 1-26. Whitenack, Bruce. RAPPeL: a requirements-analysis-process pattern language for object-oriented development. In James

Naked objects (1,258 words) [view diff] exact match in snippet view article find links to article

makes it much easier to conceive and to implement an OOUI. Easier requirements analysis. The argument here is that with the naked objects pattern, the domain

Process-data diagram (1,072 words) [view diff] exact match in snippet view article find links to article

able to model unordered activities. The example is taken from the requirements analysis workflow of the Unified Process. The main activity, “describe candidate

Metasfresh (700 words) [view diff] exact match in snippet view article find links to article

development. Consequent usage of tools to enable efficient work from requirements analysis over development and testing until build and deployment. Provide

Extended Enterprise Modeling Language (1,989 words) [view diff] case mismatch in snippet view article find links to article

Chung, and Yu (1999) : “From Object-oriented to Goal-oriented Requirements Analysis”. Communications of the ACM, January H.D. Jørgensen (2004) Interactive

Feasibility study (2,134 words) [view diff] exact match in snippet view article find links to article

definition and how it satisfies the requirements identified in the requirements analysis phase of system development. The operational feasibility assessment

Enterprise life cycle (1,122 words) [view diff] exact match in snippet view article find links to article

Handbook on Enterprise Architecture. Jeffrey O. Grady (2006). System requirements analysis Arturo Molina, Jose Manuel Sanchez, Andrew Kusiak (1998). Handbook

Guard of Honor (1,549 words) [view diff] case mismatch in snippet view article find links to article

fictional administrative command named Army Air Forces Operations and Requirements Analysis Division, acronymed AFORAD. This organization is a fictional amalgamation

Telelogic (415 words) [view diff] exact match in snippet view article find links to article

enterprise architecture tools Apr 13, 2005 Focal Point Provider of requirements analysis Dec 16, 2000 ATA Provider of project documentation & reporting tools

Steve Andriole (2,232 words) [view diff] exact match in snippet view article find links to article

variety of corporate and government clients. IIS specialized in requirements analysis and prototyping, the design of user-computer interfaces, and software

Object–role modeling (1,414 words) [view diff] exact match in snippet view article find links to article

development typically involves several stages such as: feasibility study; requirements analysis; conceptual design of data and operations; logical design; external

The Aerospace Corporation (1,815 words) [view diff] exact match in snippet view article find links to article

national-security space programs. Activities within the group include requirements analysis, cross-mission planning and architecture development, strategic

Systems development life cycle (3,158 words) [view diff] exact match in snippet view article find links to article

stage include: Need identification Feasibility analysis System requirements analysis System specification Conceptual design review During this stage

ProgramByDesign (1,789 words) [view diff] exact match in snippet view article find links to article

test-driven development, test cases are written before coding, as part of requirements analysis, rather than afterward as part of testing. Almost any human endeavour

EScholar (386 words) [view diff] exact match in snippet view article find links to article

as a subcontractor to author a feasibility study and functional requirements analysis for a data warehouse. As of this same year, the company had built

Metadata modeling (1,050 words) [view diff] exact match in snippet view article find links to article

illustrated. The example is a fragment of the process-data diagram of the requirements analysis in the Unified Process. Because both concepts are not expanded any

Operational Test and Evaluation Force (3,606 words) [view diff] exact match in snippet view article find links to article

hardware and software support, configuration control and management, requirements analysis and system analysis, design recommendations, and user training.

Ontology chart (681 words) [view diff] exact match in snippet view article find links to article

Cambridge 26–27 March. Ronald Stamper (1994). "Social norms in requirements analysis – an outline of MEASUR" Chapter 5 of Requirements Engineering: Social

Formal Aspects of Computing (546 words) [view diff] exact match in snippet view article find links to article

semantics for widely used notations and methods. Formal approaches to requirements analysis. Jim Woodcock is the current editor-in-chief. According to the Journal

Future Force Warrior (1,168 words) [view diff] exact match in snippet view article find links to article

Additional Block 3 capabilities were being defined through the requirements analysis and roadmap phase. In February 2005, the U.S. Army merged the Future

Australian Computer Society (1,305 words) [view diff] case mismatch in snippet view article find links to article

Architects, Software Quality Assurance, Women in Technology, Business Requirements Analysis, Enterprise Capacity Management, Enterprise Solution Development

Systems engineering (5,733 words) [view diff] exact match in snippet view article find links to article

spacecraft design. Systems engineering uses a host of tools that include modeling and simulation, requirements analysis, and scheduling to manage complexity.

Alistair Sutcliffe (259 words) [view diff] exact match in snippet view article find links to article

Lawrence Erlbaum Associates. Articles, a selection: — (2000). "Requirements analysis for socio-technical system design". Information Systems. 25 (3):

Semantic parameterization (606 words) [view diff] exact match in snippet view article find links to article

5, 2008. C. Potts, K. Takahashi, and A.I. Anton, "Inquiry-based requirements analysis", IEEE Software 11(2): 21–32, 1994. A. Dardenne, A. van Lamsweerde

DO-178B (1,877 words) [view diff] exact match in snippet view article find links to article

software safety analyses tasks are accomplished in sequential steps (requirements analysis, top level design analysis, detailed design analysis, code level

Deep Carbon Observatory (2,433 words) [view diff] exact match in snippet view article find links to article

using a combination of informatics methods, use case development, requirements analysis, inventories and interviews. A list of some of the scientists involved

Data quality (4,699 words) [view diff] case mismatch in snippet view article find links to article

86–95. Article Wang, R., Kon, H. & Madnick, S. (1993), Data Quality Requirements Analysis and Modelling, Ninth International Conference of Data Engineering

Story-driven modeling (1,321 words) [view diff] exact match in snippet view article find links to article

Reckord, C.; Schneider, C.; Semmelroth, S. (2006). "Using object scenarios for requirements analysis - an experience report". Modellierung 2006: 269–278.

Soft goal (202 words) [view diff] case mismatch in snippet view article find links to article

(--) Unknown S-Cube Knowledge Model: Soft Goals From Object-Oriented to Goal-Oriented Requirements Analysis, Mylopoulos John, Chung Lawrence, Yu Eric

Cisco certifications (4,069 words) [view diff] exact match in snippet view article find links to article

operations. CCDE supplies a vendor-neutral curriculum, testing business requirements analysis, design, planning, and validation practices. The course came about

Data analysis (9,569 words) [view diff] case mismatch in snippet view article find links to article

requires |journal= (help) Brackett, John W. (1989), "Performing Requirements Analysis Project Courses for External Customers", Issues in Software Engineering

Winston W. Royce (1,436 words) [view diff] case mismatch in snippet view article find links to article

model with the following seven steps: Systems requirements Software requirements Analysis Program design Coding Testing, and Operation He called them "implementation

Donald Firesmith (1,178 words) [view diff] case mismatch in snippet view article find links to article

conference papers, and tutorials A selection: 1993. Object-Oriented Requirements Analysis and Logical Design: A Software Engineering Approach, John Wiley

Deployment management (754 words) [view diff] exact match in snippet view article find links to article

use of the software or hardware that was purchased. This includes requirements analysis, scope analysis, customisations, systems integrations, user policies

Abuse case (378 words) [view diff] case mismatch in snippet view article find links to article

and Chris Fox (Dec 1999). "Using Abuse Case Models for Security Requirements Analysis" (PDF). Proceedings of the 15th Annual Computer Security Applications

Enid Mumford (4,153 words) [view diff] case mismatch in snippet view article find links to article

of an expert system. Wiley. 1995. Effective Systems Design and Requirements Analysis: the ETHICS Approach. Macmillan. 1996. Systems Design: Ethical Tools

Fieldbus (5,704 words) [view diff] exact match in snippet view article find links to article

FIP standard is based on a French initiative in 1982 to create a requirements analysis for a future field bus standard. The study led to the European Eureka

Alan M. Davis (638 words) [view diff] no match in snippet view article find links to article

members as one of the 20 classic computer science books: Software Requirements: Analysis and Specification (Prentice Hall 1990), ISBN 0-13-824673-4. Software

Non-functional requirements framework (503 words) [view diff] case mismatch in snippet view article find links to article

Mylopoulos, Chung, and Yu: “From Object-oriented to Goal-oriented Requirements Analysis" Communications of the ACM, January 1999 [CACM.f.doc [1] [2] Götz

Ronald Stamper (1,291 words) [view diff] case mismatch in snippet view article find links to article

Computer Journal 35, 368. Stamper, R. K. (1993). "Social Norms in Requirements Analysis – an outline of MEASUR." In Requirements Engineering Technical and

Artificial intelligence engineering (4,108 words) [view diff] no match in snippet view article find links to article

Artificial intelligence engineering (AI engineering) is a technical discipline that focuses on the design, development, and deployment of AI systems. AI

Wang Institute of Graduate Studies (384 words) [view diff] exact match in snippet view article find links to article

technology, principles of computer networks, programming environments, requirements analysis, software marketing, technical communication, transaction processing

Destination Earth (European Union) (927 words) [view diff] exact match in snippet view article

"Destination Earth - Use Case Analysis". It gives a state-of-the-art requirements analysis for the development and creation of digital twins. It also gives

Scenario planning (8,619 words) [view diff] exact match in snippet view article find links to article

outcomes and their implications. A scenario is a tool used during requirements analysis to describe a specific use of a proposed system. Scenarios capture

ZXID (873 words) [view diff] case mismatch in snippet view article find links to article

"Secure Business Processes in Service-Oriented Architectures – A Requirements Analysis", in Proceedings of the 8th IEEE European Conference on Web Services

Prianto (555 words) [view diff] exact match in snippet view article find links to article

outside the regular distribution portfolio. Services relating to requirements analysis, system planning, installation and training have been offered to

Joint application design (2,377 words) [view diff] case mismatch in snippet view article find links to article

2010-03-22. Bill Jennerich "Joint Application Design -- Business Requirements Analysis for Successful Re-engineering." 18:50, 26 June 2006 (UTC)[2] Last

EUCIP (819 words) [view diff] exact match in snippet view article find links to article

The Use and Management of Information Systems This area refers to requirements analysis and planning in the use of ICT within an organisation. It is therefore

Simple API for Grid Applications (1,894 words) [view diff] case mismatch in snippet view article find links to article

Informational Document, GFD.70 (pdf) Shantenu Jha, Andre Merzky: "A Requirements Analysis for a Simple API for Grid Applications", OGF Informational Document

International Requirements Engineering Conference (238 words) [view diff] case mismatch in snippet view article find links to article

Quality-Requirement Conflicts Experience 2006 Annie Antón Goal-Based Requirements Analysis Research 2007 Eric Yu Towards Modelling and Reasoning Support for

DESE Research (775 words) [view diff] exact match in snippet view article find links to article

certification; missile research and development; modeling and simulation; requirements analysis; test and evaluation; threat assessment; training; weapon system

Pascal Lee (2,359 words) [view diff] case mismatch in snippet view article find links to article

Aerial Explorers Anomalous scattering of light on Triton Empirical Requirements Analysis for Mars Surface Operations Using the Flashline Mars Arctic Research

Cap Gemini SDM (1,921 words) [view diff] exact match in snippet view article find links to article

planning: Problem definition and initial plan Definition study: Requirements analysis and revised plan Basic Design: High level technical design and revised

Arquivo Público do Estado de São Paulo (2,388 words) [view diff] exact match in snippet view article find links to article

of the State of São Paulo (PRODESP) conducted tests, performed requirements analysis, mapped and modeled documents, and developed rules for parameterization

Common Berthing Mechanism (27,457 words) [view diff] exact match in snippet view article find links to article

the point of first touch away from the chase vehicle. By 1972, requirements analysis for the Shuttle Program estimated that almost 40% of mission objectives

Implementation maturity model assessment (2,290 words) [view diff] exact match in snippet view article find links to article

implementation processes. (Rooimans et al., 2003, pp. 160–163) Requirements analysis Check dependencies In order to determine the level of an IMM-element

Robert Alan Olson (1,785 words) [view diff] case mismatch in snippet view article find links to article

Hazard mitigation plans for various municipalities to meet FEMA requirements Analysis of performance of the water system and the response of the East