HI everyone,
My name is Kumar & Iam extremely new to this forum. I had completed my MBA(Information Technology) & currently working as an junior Business Analyst in a WebApplication Software company.All I need is your Kind advice & guidance which will shapeup my future in my work.
1.First of all my company is an mid-scale type & I am the first person to Employee as an Business Analyst.
2. I dont have a proper guidance from my higher level,SO its my duty to learn about all the procedure.
3.My higher authority person gave me an existing project & asked me to prepare SRS .
So All I need is your guidance & blessings.
Hi Kumar,
Let us know what specific questions you have... If your project is not sensitive you can post the details here. I would ask your manager if he/she has any expectations on the format and/or template of the SRS (what information they expect). You also need to ask them what are your possible sources of information for the project: stakeholders, existing requirements, project charter and vision, end-users, etc.
Best of luck,
- Adrian
Adrian & Chris,
First of all I like to inform you that my company deals only webapplication projects,so they gave me an existing client requirement document which covers the whole requirement.What I want to do is to analyse the requirement properly &I need to prepare a detailed document like(Functional specifications,Technical specifications,DFD,Usecase....).Also I want to mention them pros & cons,Methods to improve the quality of documentations.This is my first task !I dont know how I will handle it.Thankyou verymuch for your instant reply.
Kumar
If this is your first job with the team I would recommend you focus on getting the job done before you start trying to improve things. The reasons for this is that you have to build up credibility before people want to hear your opinion.
So focus on getting the developers to understand the client's requirements and for the right tool to be built. Use cases can help, but more important is speaking with everybody and getting the communication flowing.
Maybe if you want to add some value by way of expertise look up some best practice UI tips and hand them across to the development team. Do it in the context of "Hey guys, look at this article I found" otherwise you'll be in danger of telling them how to do their job. (Did I mention taht you need to build up crdibility before people will let you give them advice?)
Craig
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: