Every year, organizations around the world face startlingly high project failure rates. Some research has shown that less than 30 percent of software projects are completed on time and on budget—and barely 50 percent end up meeting their proposed functionality. If you’re a big league baseball player, failing five to seven times out of ten will get ...

» A Short History of Systems Development

(709 Views) (0 Comments)

I always find it amusing when I tell a young person in this industry that I worked with punch cards and plastic templates years ago. Its kind of the same dumbfounded look I get from my kids when I tell them we used to watch black and white television with three channels, no remote control, and station signoffs at midnight. It has been my observatio...

» Functional Specification - a Tutorial

(2624 Views) (1 Comments)

What Is A Functional Specification? Functional specifications (functional specs), in the end, are the blueprint for how you want a particular web project or application to look and work. It details what the finished product will do, how a user will interact with it, and what it will look like. By creating a blueprint of the product first, time an...

» From Use Case Diagrams to Context Diagrams

(932 Views) (0 Comments)

As long as practitioners recognize that use case diagrams are optional and iconic (as opposed to schematic), they shouldn't have problems. The diagrams are useful, for example, on whiteboards as a way of sketching and framing an agenda while people are writing up and reviewing use case detail on index cards. The trouble starts, however, when pr...

» "Analysis and Design" Considered Harmful

(387 Views) (2 Comments)

This article describes a common pitfall of thinking of analysis and design together as a single process, and highlights the need to treat analysis and design as two separate processes. The author, points out that much of the UML standard, as it is explained today, is described in terms of design artifacts rather than analysis artifacts. Author: Co...

» Implicit Data Dictionaries are Dangerous!

(475 Views) (0 Comments)

Describes the difference between a data dictionary and an implicit data dictionary and why an implicit data dictionary (or no data dictionary at all) may spell trouble for your project. Can data dictionaries be used with UML Use Cases or an XP methodology? Author: Conrad Weisert

» Separating Analysis from Design

(539 Views) (0 Comments)

"Business Analysis is about thinking what your solution should do, while Design is about how to make it happen using the technology available. Don't ever combine the two - you save nothing." This paper by Brian Cooney, principal instructor at IRM, describes the need for clear separation between the two phases and the benefits this provides for a...

ARTICLE/PAPER CATEGORIES

» Activity Diagram
» Agile Methods
» Analytical and Problem Solving Skills
» Business Analysis Planning (BABOK KA)
» Business Process Management (BPM)
» Business Process Modeling Notation (BPMN)
» Career as a Business Systems Analyst
» CBAP
» Class Diagram
» Data Analysis & Modeling
» Elicitation (BABOK KA)
» Enterprise Analysis (BABOK KA)
» Estimation
» Functional Specifications
» Getting Started as a Business Systems Analyst
» IIBA & BABOK
» Interviewing & Hiring Business Systems Analysts
» Leadership & Management
» Process Improvement (CMMI, Six Sigma, SPICE, etc.)
» Project Management
» Requirements Analysis (BABOK KA)
» Requirements Management and Communication (BABOK KA)
» SDLC, Process, and Methodologies
» Security Analysis
» Service Oriented Architecture (SOA)
» Soft Skills
» Solution Assessment and Validation (BABOK KA)
» Structured Systems Analysis (DFDs, ERDs, etc.)
» Technical Topics
» Testing & Quality Assurance (QA)
» Tools
» Unified Modeling Language (UML)
» Use Cases
» User Interface & Usability
» Vertical Domain or Industry


Advertising Opportunities \| Contact Us

Privacy Statement | Terms Of Use