* MySQL. Method install, set-up and maintenance.

Don't see the one your looking for? Let us know! Got Method Resources yourself? Lets add it to the Resource Database!

Let us know:

... yours Today!

Learn more ...

About Method Resources ...

... What is Method Resources ... Software development methodology - from Wikipedia, the free encyclopedia | A software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, and extreme programming. A methodology can also include aspects of the development environment (i.e. IDEs), model-based development, computer aided software development, and the utilization of particular frameworks (i.e. programming libraries or other tools). As any software development methodology is comparable with a systematic software development process guided by certain guidelines, rules, paradigms and similar methodical activities, such a process qualifies as being described as a method. The term methodology, which is stigmatised as a buzzword, consequently breaks the logical link between the term and its intended content and therefore creating confusion. The creation and use of methods which incorporate other methods to produce an abstracter or farther scoped method (method of methods), which may even be guided by paradigms, does not qualify as methodology. A real software development methodology would, for example, require the analysis of different software development methods to identify similarities or differences in structure on a meta level, whereas the actual use of the content of the methods in a broader context is not within the scope of an methodology. See also[edit] Domain-specific modeling Lightweight methodology List of software engineering topics List of software development philosophies Object modeling language Structured programming Cowboy coding: Software development without a strict software development methodology Core activities Requirements Specification Architecture Construction Design Testing Debugging Deployment Maintenance Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP XP Agile Lean Dual Vee Model TDD FDD DDD Supporting disciplines Configuration management Documentation Quality assurance (SQA) Project management User experience Tools Compiler Debugger Profiler GUI designer Modeling IDE Build automation http://en.wikipedia.org/wiki/Software_development_methodology As a framework[edit] A software development methodology is a framework that is used to structure, plan, and control the process of developing an information system - this includes the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.[2] The three basic approaches applied to software development methodology frameworks. A wide variety of such frameworks have evolved over the years, each with its own recognized strengths and weaknesses. One software development methodology framework is not necessarily suitable for use by all projects. Each of the available methodology frameworks are best suited to specific kinds of projects, based on various technical, organizational, project and team considerations.[2] These software development frameworks are often bound to some kind of organization, which further develops, supports the use, and promotes the methodology framework. The methodology framework is often defined in some kind of formal documentation. Specific software development methodology frameworks include: Rational Unified Process (RUP, IBM) since 1998. Agile Unified Process (AUP) since 2005 by Scott Ambler As an approach[edit] The term software development methodology may also refer to an approach used to apply the software development methodology framework. Specific approaches include: 1970s Structured programming since 1969 Cap Gemini SDM, originally from PANDATA, the first English translation was published in 1974. SDM stands for System Development Methodology 1980s Structured systems analysis and design method (SSADM) from 1980 onwards Information Requirement Analysis/Soft systems methodology 1990s Object-oriented programming (OOP) developed in the early 1960s, and became a dominant programming approach during the mid-1990s Rapid application development (RAD), since 1991 Dynamic systems development method (DSDM), since 1994 Scrum, since (1995) Team software process, since (1998) Extreme programming, since (1999) Approaches[edit] Every software development methodology approach acts as a basis for applying specific frameworks to develop and maintain software. Several software development approaches have been used since the origin of information technology. Broadly these are: Software development life cycle methodology Agile methodology There are many models under these methodologies: Software development life cycle:? Waterfall: a linear framework Spiral: a combined linear-iterative framework Incremental: a combined linear-iterative framework or V Model Prototyping: an iterative framework Rapid application development (RAD): an iterative framework Agile methodology: Scrum Extreme programming Adaptive software development (ASD) Dynamic system development method (DSDM) Waterfall development[edit] The waterfall model is a sequential development approach, in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. The first formal description of the method is often cited as an article published by Winston W. Royce[3] in 1970 although Royce did not use the term "waterfall" in this article. The basic principles are:[2] Project is divided into sequential phases, with some overlap and splashback acceptable between phases. Emphasis is on planning, time schedules, target dates, budgets and implementation of an entire system at one time. Tight control is maintained over the life of the project via extensive written documentation, formal reviews, and approval/signoff by the user and information technology management occurring at the end of most phases before beginning the next phase. The Waterfall model is a traditional engineering approach applied to software engineering. It has been widely blamed for several large-scale government projects running over budget, over time and sometimes failing to deliver on requirements due to the Big Design Up Front approach. Except when contractually required, the Waterfall model has been largely superseded by more flexible and versatile methodologies developed specifically for software development. See Criticism of Waterfall model. Prototyping[edit] Software prototyping, is the development approach of activities during software development, the creation of prototypes, i.e., incomplete versions of the software program being developed. The basic principles are:[2] Not a standalone, complete development methodology, but rather an approach to handle selected parts of a larger, more traditional development methodology (i.e. incremental, spiral, or rapid application development (RAD)). Attempts to reduce inherent project risk by breaking a project into smaller segments and providing more ease-of-change during the development process. User is involved throughout the development process, which increases the likelihood of user acceptance of the final implementation. Small-scale mock-ups of the system are developed following an iterative modification process until the prototype evolves to meet the users’ requirements. While most prototypes are developed with the expectation that they will be discarded, it is possible in some cases to evolve from prototype to working system. A basic understanding of the fundamental business problem is necessary to avoid solving the wrong problem. Incremental development[edit] Various methods are acceptable for combining linear and iterative systems development methodologies, with the primary objective of each being to reduce inherent project risk by breaking a project into smaller segments and providing more ease-of-change during the development process. The basic principles are:[2] A series of mini-Waterfalls are performed, where all phases of the Waterfall are completed for a small part of a system, before proceeding to the next increment, or Overall requirements are defined before proceeding to evolutionary, mini-Waterfall development of individual increments of a system, or The initial software concept, requirements analysis, and design of architecture and system core are defined via Waterfall, followed by iterative Prototyping, which culminates in installing the final prototype, a working system. Spiral development[edit] The spiral model. The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. It is a meta-model, a model that can be used by other models. The basic principles are:[2] Focus is on risk assessment and on minimizing project risk by breaking a project into smaller segments and providing more ease-of-change during the development process, as well as providing the opportunity to evaluate risks and weigh consideration of project continuation throughout the life cycle. "Each cycle involves a progression through the same sequence of steps, for each part of the product and for each of its levels of elaboration, from an overall concept-of-operation document down to the coding of each individual program."[4] Each trip around the spiral traverses four basic quadrants: (1) determine objectives, alternatives, and constraints of the iteration; (2) evaluate alternatives; Identify and resolve risks; (3) develop and verify deliverables from the iteration; and (4) plan the next iteration.[5] Begin each cycle with an identification of stakeholders and their win conditions, and end each cycle with review and commitment.[6] Rapid application development[edit] Rapid application development (RAD) is a software development methodology, which involves iterative development and the construction of prototypes. Rapid application development is a term originally used to describe a software development process introduced by James Martin in 1991. The basic principles are:[2] Key objective is for fast development and delivery of a high quality system at a relatively low investment cost. Attempts to reduce inherent project risk by breaking a project into smaller segments and providing more ease-of-change during the development process. Aims to produce high quality systems quickly, primarily via iterative Prototyping (at any stage of development), active user involvement, and computerized development tools. These tools may include Graphical User Interface (GUI) builders, Computer Aided Software Engineering (CASE) tools, Database Management Systems (DBMS), fourth-generation programming languages, code generators, and object-oriented techniques. Key emphasis is on fulfilling the business need, while technological or engineering excellence is of lesser importance. Project control involves prioritizing development and defining delivery deadlines or “timeboxes”. If the project starts to slip, emphasis is on reducing requirements to fit the timebox, not in increasing the deadline. Generally includes joint application design (JAD), where users are intensely involved in system design, via consensus building in either structured workshops, or electronically facilitated interaction. Active user involvement is imperative. Iteratively produces production software, as opposed to a throwaway prototype. Produces documentation necessary to facilitate future development and maintenance. Standard systems analysis and design methods can be fitted into this framework. Other practices[edit] Other methodology practices include: Object-oriented development methodologies, such as Grady Booch's object-oriented design (OOD), also known as object-oriented analysis and design (OOAD). The Booch model includes six diagrams: class, object, state transition, interaction, module, and process.[7] Top-down programming: evolved in the 1970s by IBM researcher Harlan Mills (and Niklaus Wirth) in developed structured programming. Unified Process (UP) is an iterative software development methodology framework, based on Unified Modeling Language (UML). UP organizes the development of software into four phases, each consisting of one or more executable iterations of the software at that stage of development: inception, elaboration, construction, and guidelines. Many tools and products exist to facilitate UP implementation. One of the more popular versions of UP is the Rational Unified Process (RUP). Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve via collaboration between self-organizing cross-functional teams. The term was coined in the year 2001 when the Agile Manifesto was formulated. Slow programming, as part of the larger Slow Movement, emphasizes careful and gradual work without (or minimal) time pressures. Slow programming aims to avoid bugs and overly quick release schedules. Subtopics[edit] View model[edit] The TEAF Matrix of Views and Perspectives. A view model is a framework that provides the viewpoints on the system and its environment, to be used in the software development process. It is a graphical representation of the underlying semantics of a view. The purpose of viewpoints and views is to enable human engineers to comprehend very complex systems, and to organize the elements of the problem and the solution around domains of expertise. In the engineering of physically intensive systems, viewpoints often correspond to capabilities and responsibilities within the engineering organization.[8] Business process and data modelling[edit] Graphical representation of the current state of information provides a very effective means for presenting information to both users and system developers. example of the interaction between business process and data models.[9] A business model illustrates the functions associated with the business process being modeled and the organizations that perform these functions. By depicting activities and information flows, a foundation is created to visualize, define, understand, and validate the nature of a process. A data model provides the details of information to be stored, and is of primary use when the final product is the generation of computer software code for an application or the preparation of a functional specification to aid a computer software make-or-buy decision. See the figure on the right for an example of the interaction between business process and data models.[9] Computer-aided software engineering[edit] Computer-aided software engineering (CASE), in the field software engineering is the scientific application of a set of tools and methods to a software which results in high-quality, defect-free, and maintainable software products.[10] It also refers to methods for the development of information systems together with automated tools that can be used in the software development process.[11] The term "computer-aided software engineering" (CASE) can refer to the software used for the automated development of systems software, i.e., computer code. The CASE functions include analysis, design, and programming. CASE tools automate methods for designing, documenting, and producing structured computer code in the desired programming language.[12] Integrated development environment[edit] Anjuta, a C and C++ IDE for the GNOME environment An integrated development environment (IDE) also known as integrated design environment or integrated debugging environment is a software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a: source code editor, compiler and/or interpreter, build automation tools, and debugger (usually). Modeling language[edit] A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure. A modeling language can be graphical or textual.[14] Graphical modeling languages use a diagram techniques with named symbols that represent concepts and lines that connect the symbols and that represent relationships and various other graphical annotation to represent constraints. Textual modeling languages typically use standardised keywords accompanied by parameters to make computer-interpretable expressions. Example of graphical modelling languages in the field of software engineering are: Business Process Modeling Notation (BPMN, and the XML form BPML) is an example of a process modeling language. EXPRESS and EXPRESS-G (ISO 10303-11) is an international standard general-purpose data modeling language. Extended Enterprise Modeling Language (EEML) is commonly used for business process modeling across layers. Flowchart is a schematic representation of an algorithm or a stepwise process, Fundamental Modeling Concepts (FMC) modeling language for software-intensive systems. IDEF is a family of modeling languages, the most notable of which include IDEF0 for functional modeling, IDEF1X for information modeling, and IDEF5 for modeling ontologies. LePUS3 is an object-oriented visual Design Description Language and a formal specification language that is suitable primarily for modelling large object-oriented (Java, C++, C#) programs and design patterns. Specification and Description Language(SDL) is a specification language targeted at the unambiguous specification and description of the behaviour of reactive and distributed systems. Unified Modeling Language (UML) is a general-purpose modeling language that is an industry standard for specifying software-intensive systems. UML 2.0, the current version, supports thirteen different diagram techniques, and has widespread tool support. Programming paradigm[edit] A programming paradigm is a fundamental style of computer programming, in contrast to a software engineering methodology, which is a style of solving specific software engineering problems. Paradigms differ in the concepts and abstractions used to represent the elements of a program (such as objects, functions, variables, constraints...) and the steps that comprise a computation (assignations, evaluation, continuations, data flows...). Software framework[edit] A software framework is a re-usable design for a software system or subsystem. A software framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project. Various parts of the framework may be exposed via an API. Software development process[edit] A software development process is a framework imposed on the development of a software product. Synonyms include software life cycle and software process. There are several models for such processes, each describing approaches to a variety of software development process methodologies. Many of them are in the defense industry, which in the U.S. requires a rating based on 'process models' to obtain contracts. The international standard describing the method to select, implement and monitor the life cycle for software is ISO/IEC 12207. http://en.wikipedia.org/wiki/Software_development_methodology Software-Development Methodologies and Visual Studio Team System msdn.microsoft.com/en-us/library/aa905317 There are many methodologies for different software-development life cycles. To implement these effectively, it is important to have life-cycle tools that automate ... Software-Development Methodologies and Visual Studio Team System 11 out of 13 rated this helpful - Rate this topic From Documents to Automation Sanjay Narang October 2006 Applies to: Microsoft Visual Studio Team System Microsoft SQL Server 2005 Summary: There is a diverse set of methodologies for different types of software-development life cycles. To implement these methodologies effectively and consistently, it is important to have life-cycle tools that automate the processes and artifacts of the methodologies. Microsoft Visual Studio Team System (VSTS) provides a compelling solution for methodology management and automation. (12 printed pages) Introduction Software-development life-cycle methodologies provide the what (processes and deliverables), how (techniques), and who (roles) for every typical role in a software-development project, such as solution architects, business consultants, and developers. Over the years, the software industry has matured to a great extent in terms of the methodologies used. Today, the industry has quite a number of established and proven software-development methodologies that cater to different kinds of project life cycles: Microsoft Solution Framework (MSF), Rational Unified Process (RUP), Waterfall, Agile, and so forth. To use these methodologies effectively, it is important to follow the processes defined in the methodologies in a consistent manner across all projects. Following the software-development processes in a consistent and accurate manner is a challenging task because: Software-development processes are complex, involving many levels of interdependent activities. Most of the processes and methodologies are available as reference documents only. It is difficult for practitioners to learn the exact processes from the document references and follow them in their projects. Practitioners follow the processes manually and submit the required data into various life-cycle tools that do not have much integration with the engineering tools. The life-cycle tools could be isolated tools for project management, requirement management, bug tracking, or review management, whereas the engineering tools could be separate tools for activities such as designing, coding, testing, or Integrated Development Environments (IDE) such as Visual Studio. These different sets of tools make it difficult to have a consistent methodology implementation across multiple projects, and generate inconsistent data and reports in the organization. Inconsistency makes the process analysis unreliable, thus making it difficult to identify the process improvements. Also, as the processes are followed manually, data collection and reporting become manual tasks, which results in lower productivity and delivery efficiency. These problems can be addressed to a large extent by automating the implementation of methodologies using the life-cycle tools provided by different vendors like Microsoft Corporation and Borland. Microsoft offers Visual Studio Team System (VSTS), an integrated environment that covers most of the activities involved in a software-development project, including life-cycle management and automation. http://msdn.microsoft.com/en-us/library/aa905317.aspx Software Development Methodology www.hyperthot.com/pm_sdm.htm Software Development Methodology. ... You can see how it wouldn't take long to fill a number of big binders with development processes and procedures. Software Development Methodology a.k.a. System Development Life Cycle Click Here to View Video on YouTube: 5-Steps to Project Success Download this Free Video (Same as above) (9MB file) RIGHT Click & Save Target As: "5-Steps to Project Success - Seriously_v1.1" You have permission to freely copy and distribute this video. Read this page translated into Spanish Methodologies: What and Why? Software engineering is the practice of using selected process techniques to improve the quality of a software development effort. This is based on the assumption, subject to endless debate and supported by patient experience, that a methodical approach to software development results in fewer defects and, therefore, ultimately provides shorter delivery times and better value. The documented collection of policies, processes and procedures used by a development team or organization to practice software engineering is called its software development methodology (SDM) or system development life cycle (SDLC). Methodology as Risk Management The challenge in selecting and following a methodology is to do it wisely -- to provide sufficient process disciplines to deliver the quality required for business success, while avoiding steps that waste time, squander productivity, demoralize developers, and create useless administrivia. The best approach for applying a methodology is to consider it as a means to manage risk. You can identify risks by looking at past projects. If your organization has been plagued by problems resulting from poor requirements management, then a robust requirements management methodology would be well advised. Once this problem has been solved, through a repeatable process, the organization might then streamline its process, while ensuring that quality is maintained. Every step along the system development life cycle has its own risks and a number of available techniques to improve process discipline and resulting output quality. Moving through the development life cycle, you might encounter the following major steps: Project charter and business case Definition of the business process and business requirements Documentation of user, functional and system requirements Top level architecture, technical approach, and system design System decomposition into component and unit specifications and design Coding, unit test planning, and unit test Generation of test data for unit testing and system testing System integration and testing Implementation, delivery and cut-over Training and user support System upgrades and routine software maintenance In addition, you might have support activities throughout the development effort such as: Configuration management (version identification, baseline management and change control) Requirements management and tracability Quality management (quality assurance, quality reviews, defect tracking) System engineering reviews (requirements review, prelim. and critical design reviews, etc.) Support environment (development tools, libraries, files management, data management) Written guidance for all these steps would constitute the core of your methodology. You can see how it wouldn't take long to fill a number of big binders with development processes and procedures. Hence, the importance of selecting processes wisely - to address known risks - keeping the methodology streamlined, and allowing for some discretion on the part of the project team. http://www.hyperthot.com/pm_sdm.htm TechJini Application development process. Agile software ... www.techjini.com/ourapproach-methodologies.html TechJini follows both the Agile and the waterfall methods. The Agile methodology treats the time-to-market as the most important feature while Waterfall methodology ... me > Our Approach > Process Methodologies Methodologies TechJini follows both the Agile and the waterfall methods. The Agile methodology treats the time-to-market as the most important feature while Waterfall methodology treats the collective feature set as the most important. Our team can adapt to work in either method, depending on your situation and requirements. Agile software development processes are built on the foundation of iterative development. To that foundation we add a lighter, more people-centric viewpoint than traditional approaches. Agile processes use feedback, rather than planning, as their primary control mechanism. The feedback is driven by regular tests and releases of the evolving software. The waterfall model shows a process, where we follow a step-by-step approach towards the project. We follow this methodology when we feel that Clients practice is defined and their requirements will not change during the course of the project. After each step is perfectly finished, the process proceeds to the next step, just as builders don't revise the foundation of a house after the framing has been erected. http://www.techjini.com/ourapproach-methodologies.html Software Development Methodology | Methodology Stages ... www.cybage.com/…ages/methodologies/methodology.aspx Cybage have expertise in executing application development projects using Cybage Software Development Methodology. Methodologies Cybage has proven expertise in executing application development projects using Cybage Software Development Methodology. Our methodology provides a consistent way of executing and delivering projects. It provides uniform terminology and expectations for all stakeholders of the project. Our methodology coupled with our model, allows clients the flexibility to have the solutions developed and delivered with the highest levels of quality and cost efficiency through offshore development, onsite development or by combination of these components. Cybage Methodology Stages Initiation Phase (Scoping, Feasibility, Proposal) Requirement/System Study Analysis Design Construction and Unit Testing System Testing Deployment, Acceptance Testing and Knowledge Transfer Warranty Maintenance and Support The Cybage Software Development Methodology not only provides structure, but it also provides guidelines for tailoring alternatives for standard approach, to suit different client requirements and processes. The core strength of our methodology is that after tailoring and blending with client's processes, it is zero learning for the client as processes remain same for them. The framework of our methodology allows us to adopt a variety of techniques and tools for carrying out the defined tasks. It also allows us to change techniques and/or tools as new products come onto the market without changing the methodology. By re-utilizing clearly defined processes and tasks, our methodology simplifies the development process. The sequencing of those tasks and the completeness of those deliverables have been previously proven, thereby ensuring clarity and certainty to the process. Our methodology's proven experience ensures that there are no holes to be overlooked or tasks to be duplicated. Our decision to document our software development methodology stems from the belief that before you can improve a process, you must document it. This document demonstrates that we have a documented process for building software. Our intention is to identify and improve the software development life cycle we use to build software. It is important to note that our methodology is an evolving methodology that is revised on an ongoing basis. It is not to be considered etched in stone, but is to act as a guideline and is to be used in accordance with the needs of the current project. http://www.cybage.com/pages/methodologies/methodology.aspx

... How To Method Resources.

Learn more > about the Resource Network, or about Us ...

the Bulletin Board

INSTRUCTIONS Enter questions, comments and link info in the NotePad, NOTE - we do NOT automatically capture e-mail address - you must enter it.   EDITing is up to you, what you submit is what gets posted.   To request further maintenance -or- for more private communications, use the FeedBack form below.   Post Here   Who are you: Where are you from: What would you like to say: