Functional Specifications

Nov 26, 2017
2914 Views
13 Likes
0 Comments

The purpose of this article is to explore feature files. Feature files are documents that contain those Gherkin scenarios & requirements – they can be very useful to teams working on BDD projects. Feature files may be a key deliverable for BAs.  Feature files are where BAs store requirements & can create the bridge between requirements and automated tests (more on that later).

Jul 23, 2017
8103 Views
16 Likes
1 Comments

Trying to secure a business analyst job interview in an area in which you don’t have prior experience can be a huge challenge. It’s common for recruiters and hiring managers to screen out applicants--no matter how accomplished they seem to be from their resumes--simply because the candidate’s job history doesn’t include work in the target industry...  But how do you get your foot in the door when so many recruiters and hiring managers tend to ignore applications from a candidate whose background doesn’t match the role they are trying to fill? The following tips may help.

Mar 19, 2017
11376 Views
14 Likes
0 Comments

A business analyst is a person who analyzes, organizes, explores, scrutinizes and investigates an organization and documents its business and also assesses the business model and integrates the whole organization with modern technology. The Business Analyst role is mostly about documenting, verifying, recording and gathering the business requirements and its role is mostly associated with the information technology industry.

Dec 28, 2016
10976 Views
10 Likes
0 Comments
A story is defined as a narrative or tale, true or imaginary. Each story has a moral hidden in it. A story writer won't directly say that hard work and patience is the key to success. Instead the writer came up with a story of Hare and Tortoise. And if we observe carefully, stories are everywhere; we ask a friend about her love story, we watch a prime time news story, we ask a new friend about his life's story, the movie I watched the other day had a good story. 
15738 Views
0 Likes
2 Comments
Data migration is typically the most forgotten or underestimated component of an IT project which is the process of making a copy of data and moving it from one system to another, preferably without disrupting or disabling active business processes. On some occasions, it is not easy to understand that a data migration is needed in the project and ...
30843 Views
15 Likes
0 Comments
The 3 Amigos (sometimes referred to as a “Specification Workshop”) is a meeting where the Business Analyst presents requirements and test scenarios (collectively called a “feature”) for review by a member of the development team and a member of the quality assurance team.
49123 Views
38 Likes
1 Comments

At UC Berkeley there has been an increasing awareness of the importance of business analysis (BA) and user experience (UX) in the software development lifecycle. In this article we will discuss the advantages of involving BA and UX practitioners in your development process, when and how to involve them, and the similarities and differences between the two professions.

62109 Views
118 Likes
7 Comments

The structure of business analysis documents isn't a commonly discussed topic. This article will show what documents are produced by a BA and the main sections they contain.

These are the main documents produced by a BA over the course of a project...
 

13954 Views
7 Likes
3 Comments

Business requirements are usually captured in narratives and graphics that, regardless of how detailed, structured, cross-referenced and validated, are fundamentally imprecise. A data-driven approach to specifications has the potential to help avoid these problems and subsequently decrease the risk and increase the return on companies' IT investments.

9854 Views
2 Likes
1 Comments

Is documentation a blessing or a curse? If you’re working on an agile project does it get in the way? If you’re updating a core system that runs your company’s business, are you cursing the analyst who didn’t adequately document all the business functionality? Is today’s agile project tomorrow’s core system?

9823 Views
5 Likes
0 Comments

A user of almost any given software system or business application will require precise analytics in order to objectively measure its effectiveness, or the effectiveness of an associated product. These analytics –or reports—therefore, must measure the right criteria at the right time(s) in the right way in order to be useful to the user. For that reason, any newly proposed reporting function requires careful, measured, thoughtful and thoroughly vetted requirements in order to ensure its efficacy.

47171 Views
437 Likes
3 Comments

Business analysis is an important aspect of agile software development projects, but the agile approach is significantly different than the traditional, serial approach of yesteryear. Because the agile approach to business analysis is different the approach to requirements specification is also different, for many traditionalists this will prove to be a significant cultural shock to them at first. In this article I briefly overview how business analysis activities fit into an agile approach, question some of the dogma around documentation within the traditional community, summarize some of the evidence showing that agile approaches are more effective in practice than traditional approaches, and end with strategies for specifying requirements on an agile project.

114706 Views
4 Likes
3 Comments
Ideally, an agile document is just barely good enough, or just barely sufficient, for the situation at hand. Documentation is an important part of agile software development projects, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall projec...
15013 Views
2 Likes
0 Comments

Defining specifications for the design and development of systems and software is a lot like this classic Gershwin song and what I personally regard as the biggest cause of confusion in the Information Technology field for as long as I can remember, which is over 30 years in the industry.  Some people say specifications should be based on the inherent properties of information, others believe it is based on a screen/report or file layout, yet others adamantly believe it should be based on process and data specifications.  Interestingly, all are absolutely correct.  The difference lies in the perspective of the person and the work to be performed.  For example, how we define specifications for the design of an automobile is certainly different than how we specify a skyscraper.  The same is true in the I.T. field where we have different things to be produced by different people.

Author: Tim Bryce

25865 Views
16 Likes
2 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...
Page 1 of 2First   Previous   [1]  2  Next   Last   


Upcoming Live Webinars



Latest Articles

Does design belong in your requirements?
Dec 17, 2017
0 Comments
I don’t know how many articles I’ve read where the author states requirements should be “what” the user/client needs, not &ldq...

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