4868 Views
1 Likes
0 Comments
The work of a business analyst is to develop an understanding of business process and model them. Usually the work is associated with a project whose objectives are to change or improve a process. Often these processes are quite complex and the analyst must get the information from many sources. Usually much of the information and ideas for improve...
3229 Views
1 Likes
0 Comments
Agile Modeling (AM) defines a collection of core and supplementary principles that when applied on a software development project set the stage for a collection of modeling practices. Some of the principles have been adopted from eXtreme Programming (XP) and are well documented in Extreme Programming Explained, which in turn adopted them from commo...
5368 Views
1 Likes
0 Comments
One of the unfortunate aspects of industry-level paradigm shifts, such as what we're seeing with the move to agile software development, is that the followers of the incumbent paradigm often get to set the tone of the conversation. A perfect example of this is that traditionalists will often claim that agile approaches are riskier than traditional ...
8930 Views
1 Likes
0 Comments
Several software projects are over budgeted or have to face failures during operations. One big reason of this is Software Company develops wrong software due to wrong interpretation of requirements. Requirements engineering is one of the well known discipline within Software engineering which deals with this problem. RE is the process of eliciti...
15510 Views
9 Likes
3 Comments
Business Analysis is a straightforward process of analysing business change requirements. Why, then, are there so many methods, approaches, techniques and tools for doing what is – essentially – the same job? In order to understand this, we need to rewind a bit in time to look at where Business Analysis came from, where it currently is ...
6964 Views
0 Likes
3 Comments
Extreme programming (XP) introduced the practice of expressing requirements in the form of user stories, short descriptions of functionality–told from the perspective of a user–that are valuable to either a user of the software or the customer of the software. The following are typical user stories for a job posting and search site: ...
7440 Views
0 Likes
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...
5577 Views
1 Likes
0 Comments

I was recently helping a friend staff a fairly large project with a team of very experienced, very skilled people. I mentioned that people were really excited about the opportunity. He asked me “Why are they excited? What is it about this project that makes people want to work on it?”

That led us to a discussion about teams of highly skilled people and what motivates them to want to work on a project.

Author: Geri Schneider Winters

* Article used with permission from Wyyzzk, Inc.’s Resources for Business Analysts site at http://www.writingusecases.com This website of reports and tips contains information to help you succeed as a Business Analyst in IT.

5212 Views
0 Likes
1 Comments
There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the c...
7760 Views
0 Likes
0 Comments
The requirements engineering phase of software development projects is characterised by the intensity and importance of communication activities. During this phase, the various stakeholders must be able to communicate their requirements to the analysts, and the analysts need to be able to communicate the specifications they generate back to the sta...
6441 Views
2 Likes
0 Comments
We know that we must involve all the stakeholders if we want to discover a project’s requirements. But we need some guidelines on how to involve the right people and, given how busy everyone is, how to minimize the time and maximize the result. In this article, requirements expert Ellen Gottesdiener (www.ebgconsulting.com) shares her consider...
16219 Views
7 Likes
0 Comments
A whitepaper written by requirements expert Ellen Gottesdiener of EBG Consulting (www.ebgconsulting.com) for IBM/Rational Software. As an analyst, you have the crucial task of defining the requirements for software that is to be built or acquired. Your task is crucial for a number of reasons. If software teams fail to define excellent requirements...
4960 Views
3 Likes
0 Comments
A set of 25 serious (and somewhat cynical) guides for abusing use cases by requirements expert Ellen Gottesdiener, of EBG Consulting, Inc. (www.ebgconsulting.com). Author: Ellen Gottesdiener
12980 Views
3 Likes
0 Comments
In the Unified Modeling Language (UML), use cases are visually represented as ellipses. However, in spite of its popularity and size, UML has little of practical use to offer modelers beyond this simple iconic representation. Trying to capture and present requirements using just use case diagrams can often render the otherwise useful technique of u...
11253 Views
12 Likes
0 Comments
A fundamental reality of application development is that the user interface is the system to the users. What users want is for developers to build applications that meet their needs and that are easy to use. Too many developers think that they are artistic geniuses – they do not bother to follow user interface design standards or invest the e...
Page 72 of 77First   Previous   67  68  69  70  71  [72]  73  74  75  76  Next   Last   

 



 




Copyright 2006-2022 by Modern Analyst Media LLC