4729 Views
2 Likes
0 Comments
Now that you've read all about why you need a spec and what a spec has in it, let's talk about who should write them. Who writes specs? Let me give you a little Microsoft history here. When Microsoft started growing seriously in the 1980s, everybody there had read The Mythical Man-Month, one of the classics of software management. (If you haven'...
4488 Views
2 Likes
0 Comments
This series of articles is about functional specifications, not technical specifications. People get these mixed up. I don't know if there's any standard terminology, but here's what I mean when I use these terms. A functional specification describes how a product will work entirely from the user's perspective. It doesn't care how the thing is i...
4434 Views
1 Likes
0 Comments
It seems that specs are like flossing: everybody knows they should be writing them, but nobody does. Why won't people write specs? People claim that it's because they're saving time by skipping the spec-writing phase. They act as if spec-writing was a luxury reserved for NASA space shuttle engineers, or people who work for giant, established insu...
5471 Views
10 Likes
0 Comments
Customers are never thrilled to find out they can’t get all the features they want in release 1.0 of a new software product (at least, not if they want the features to work). However, if the development team cannot deliver every requirement by the scheduled initial delivery date, the project stakeholders must agree on which subset to implemen...
3444 Views
2 Likes
0 Comments
The path to quality software begins with excellent requirements. Slighting the processes of requirements development and management is a common cause of software project frustration and failure. This article describes ten common traps that software projects can encounter if team members and customers don’t take requirements seriously. I descr...
3831 Views
0 Likes
0 Comments
Information System Development (or even the broader Information Technology field) is a relatively new discipline compare to matured disciplines like mathematics, physics or philosophy. It is difficult to find an agreed-upon definition on even a widely used term such as JAD. It can mean different things to different people, and it’s constantly evolv...
4519 Views
0 Likes
0 Comments
As outsourcing, global commerce and constantly improving technology continue to change the business world, specialized professionals like scientists, engineers and information technology (IT) workers (including business systems analysts) are increasingly being asked to take on more business-oriented tasks. These tasks can include communicating...
4196 Views
0 Likes
0 Comments
Beware of the colleague or supplier who spends large amounts of time in meetings discussing the format, sequence, and wording of documents they will deliver and very little time on the actual content. Strategically, substance is what counts. In this issue of Strategic Software Engineering I will point to some common problems when form becomes a hig...
3978 Views
0 Likes
0 Comments
Some days, you wish you had telepathy. You just know that your development staff is holding back in some way, but you don’t know how to get them to communicate. Is the project in trouble, but they’re afraid to tell you? Since your software development staff won’t tell you what they’re really thinking, I asked them to confide in us instead. I pose...
5441 Views
1 Likes
0 Comments
This article proposes innovative ways to combine three of the most important methodologies that have emerged in the past decade in the field of information systems architecture: UML, RUP, and the Zachman Framework. Over the past decade, the advantages of using the Unified Modeling Language (UML) for modeling software applications have become clea...
7672 Views
3 Likes
2 Comments
Author: Derrick Brown and Jan Kusiak This extract from IRM’s training material looks at how systematic, creative thinking techniques can be used to design practical solutions to business problems. The first step in developing a solution is to identify and define the problem - see the IRM paper Problem Analysis Techniques. Using the problem definit...
9937 Views
6 Likes
2 Comments
The research work of Wil van der Aalst, Arthur ter Hofstede, Bartek Kiepuszewski, and Alistair Barros has resulted in the identification of 21 patterns that describe the behavior of business processes. This paper reviews how two graphical process modeling notations, the BPMN Business Process Diagram from the Business Process Management Initiative...
5293 Views
1 Likes
0 Comments
This tutorial/white paper introduces business process modeling using the BPMN process modeling standard. This session will show how BPMN can support different methodologies as well as different modeling goals (e.g., orchestration and choreography), using actual business processes as examples. Sample business models will also be presented and explor...
7112 Views
3 Likes
0 Comments
This extract from IRM's training material looks at how a structured approach to defining and analysing problems can be used as the basis for designing better solutions. Part 1 of this paper looks at problem definition. Part 2 introduces the reader to analytical techniques for determining the root cause of a problem. Future papers in this series wil...
6987 Views
2 Likes
0 Comments
The Business Process Modeling Notation (BPMN) has been developed to enable business user to develop readily understandable graphical representations of business processes. BPMN is also supported with appropriate graphical object properties that will enable the generation of executable BPEL. Thus, BPMN creates a standardized bridge for the gap betwe...
Page 60 of 60First   Previous   51  52  53  54  55  56  57  58  59  [60]  Next   Last   




Latest Articles

Agile User Interface Design
Sep 24, 2017
0 Comments
The role of design still puzzles many agile teams I work with. When should the design activities take place? Who should carry them out? How are design...

Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC