|
Reverse Semantic Traceability
Reverse semantic traceability (RST) is a quality control method for verification improvement that helps to insure high quality of artifacts by backward translation at each stage of the software development process. Brief introduction Each stage of development process can be treated as a series of “translations” from one language to another. At the very beginning a project team deals with customer’s requirements and expectations expressed in natural language. These customer requirements sometimes might be incomplete, vague or even contradictory to each other. The first step is specification and formalization of customer expectations, transition (“translation”) of them into a formal requirement document for the future system. Then requirements are translated into system architecture and step by step the project team generates code written in a very formal programming language. There is always a threat of inserting mistakes, misinterpreting or losing something during th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Quality Control
Quality control (QC) is a process by which entities review the quality of all factors involved in production. ISO 9000 defines quality control as "a part of quality management focused on fulfilling quality requirements". This approach places emphasis on three aspects (enshrined in standards such as ISO 9001): # Elements such as controls, job management, defined and well managed processes, performance and integrity criteria, and identification of records # Competence, such as knowledge, skills, experience, and qualifications # Soft elements, such as personnel, integrity, confidence, organizational culture, motivation, team spirit, and quality relationships. Inspection is a major component of quality control, where physical product is examined visually (or the end results of a service are analyzed). Product inspectors will be provided with lists and descriptions of unacceptable product defects such as cracks or surface blemishes for example. History and introduction Ea ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Reverse Engineering
Reverse engineering (also known as backwards engineering or back engineering) is a process or method through which one attempts to understand through deductive reasoning how a previously made device, process, system, or piece of software accomplishes a task with very little (if any) insight into exactly how it does so. It is essentially the process of opening up or dissecting a system to see how it works, in order to duplicate or enhance it. Depending on the system under consideration and the technologies employed, the knowledge gained during reverse engineering can help with repurposing obsolete objects, doing security analysis, or learning how something works. Although the process is specific to the object on which it is being performed, all reverse engineering processes consist of three basic steps: Information extraction, Modeling, and Review. Information extraction refers to the practice of gathering all relevant information for performing the operation. Modeling refers to th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Quality Control
Quality control (QC) is a process by which entities review the quality of all factors involved in production. ISO 9000 defines quality control as "a part of quality management focused on fulfilling quality requirements". This approach places emphasis on three aspects (enshrined in standards such as ISO 9001): # Elements such as controls, job management, defined and well managed processes, performance and integrity criteria, and identification of records # Competence, such as knowledge, skills, experience, and qualifications # Soft elements, such as personnel, integrity, confidence, organizational culture, motivation, team spirit, and quality relationships. Inspection is a major component of quality control, where physical product is examined visually (or the end results of a service are analyzed). Product inspectors will be provided with lists and descriptions of unacceptable product defects such as cracks or surface blemishes for example. History and introduction Ea ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
P-Modeling Framework
P-Modeling Framework is a package of guidelines, methods, tools and templates for the development process improvement. P-Modeling framework can be integrated into any other SDLC in use, e.g., MSF Agile, MSF CMMI, RUP, etc. History The origins of P-Modeling Framework come from "The Babel Experiment" designed by Vladimir L. Pavlov in 2001 as a training program for software engineering students that was aimed at making students go through a “condensed” version of communication problems typical for software development and gain the experience of applying UML to overcome these problems. This experiment was done in the following manner. A team of students was assigned the task of designing a software system with the following restriction factor: UML had to be the only language allowed for communication while working on the project. The premise was intended to make students go through a “condensed” version of communication problems typical for software development and gai ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Project Plan
A project plan, according to the Project Management Body of Knowledge (PMBOK), is: "...a formal, approved document used to guide both ''project execution'' and ''project control''. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among ''project stakeholders'', and document approved scope, cost, and schedule ''baselines''. A project plan may be summarized or detailed." The latest edition of the PMBOK (v6) uses the term ''project charter'' to refer to the contract that the project sponsor and project manager use to agree on the initial vision of the project (scope, baseline, resources, objectives, etc.) at a high level. In the PMI methodology described in the PMBOK v5, the project charter and the project management plan are the two most important documents for describing a project during the initiation and planning phases. PRINCE2 defines a project plan as: :"...a statement of how and when a project's objectives ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
User Interface
In the industrial design field of human–computer interaction, a user interface (UI) is the space where interactions between humans and machines occur. The goal of this interaction is to allow effective operation and control of the machine from the human end, while the machine simultaneously feeds back information that aids the operators' decision-making process. Examples of this broad concept of user interfaces include the interactive aspects of computer operating systems, hand tools, heavy machinery operator controls and process controls. The design considerations applicable when creating user interfaces are related to, or involve such disciplines as, ergonomics and psychology. Generally, the goal of user interface design is to produce a user interface that makes it easy, efficient, and enjoyable (user-friendly) to operate a machine in the way which produces the desired result (i.e. maximum usability). This generally means that the operator needs to provide minimal input ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Test Case
In software engineering, a test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test cases underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce the desired coverage of the software being tested. Formally defined test cases allow the same tests to be run repeatedly against successive versions of the software, allowing for effective and consistent regression testing. Formal test cases In order to fully test that all the requirements of an application are met, there must be at least two test cases for each requirement: one positive test and one negative test. If a requirement has sub-requirements, each sub-requirement must have at least two test cases. Keeping track of the link between t ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
System Architecture
A system architecture is the conceptual model that defines the structure, behavior, and more views of a system. An architecture description is a formal description and representation of a system, organized in a way that supports reasoning about the structures and behaviors of the system. A system architecture can consist of system components and the sub-systems developed, that will work together to implement the overall system. There have been efforts to formalize languages to describe system architecture, collectively these are called architecture description languages (ADLs). Overview Various organizations can define systems architecture in different ways, including: * The fundamental organization of a system, embodied in its components, their relationships to each other and to the environment, and the principles governing its design and evolution. * A representation of a system, including a mapping of functionality onto hardware and software components, a mapping of the softw ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Functional Requirement
In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a specification of behavior between inputs and outputs. Functional requirements may involve calculations, technical details, data manipulation and processing, and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describe all the cases where the system uses the functional requirements, these are captured in use cases. Functional requirements are supported by non-functional requirements (also known as "quality requirements"), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system must do ," while non-functional requirements take the form "system shall be ." The plan for implementing functional requirements is detailed in the system design, where ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Deliverable
A deliverable is a tangible or intangible good or service produced as a result of a project that is intended to be delivered to a customer (either internal or external). A deliverable could be a report, a document, a software product, a server upgrade or any other building block of an overall project.Cutting, Thomas.Deliverable-based Project Schedules: Part 1. PMHut.com (Last accessed 8 November 2009). A deliverable may be composed of multiple smaller deliverables. It may be either an outcome to be achieved (as in "The corporation says that becoming profitable this year is a deliverable") or an output to be provided (as in "The deliverable for the completed project consists of a special-purpose electronic device and its controlling software"). Some deliverables are dependent on other deliverables being completed first; this is common in projects with multiple successive milestones. In this way many time-savings are possible, shortening greatly the whole project final supply term. T ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Vision Document
A vision statement is an inspirational statement of an idealistic emotional future of a company or group. Vision describes the basic human emotion that a founder intends to be experienced by the people the organization interacts with. The Infinite Game Vision statements may fill the following functions for a company: * Serve as foundations for a broader strategic plan. * Motivate existing employees and attract potential employees by clearly categorizing the company's goals and attracting like-minded individuals. * Focus company efforts and facilitate the creation of core competencies by directing the company to only focus on strategic opportunities that advance the company's vision. * Help companies differentiate from competitors. A consensus does not exist on the characteristics of a "good" or "bad" vision statement. Commonly cited traits include: * concise: able to be easily remembered and repeated * clear: defines a prime goal * Time horizon: defines a time horizon * futur ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Policy
Policy is a deliberate system of guidelines to guide decisions and achieve rational outcomes. A policy is a statement of intent and is implemented as a procedure or protocol. Policies are generally adopted by a governance body within an organization. Policies can assist in both ''subjective'' and ''objective'' decision making. Policies used in subjective decision-making usually assist senior management with decisions that must be based on the relative merits of a number of factors, and as a result, are often hard to test objectively, e.g. work–life balance policy... Moreover, Governments and other institutions have policies in the form of laws, regulations, procedures, administrative actions, incentives and voluntary practices. Frequently, resource allocations mirror policy decisions. Policy is a blueprint of the organizational activities which are repetitive/routine in nature. In contrast, policies to assist in objective decision-making are usually operational in nature an ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
