10 Essentials Steps Of Requirement Analysis Of Social Media Reports

  1. Prepare Plan Of Requirement Analysis:
    Create a simple but great Project Plan dedicated to Requirement Analysis of your Social Media Reports and Social Media Dashboard in details. Include a complete schedule of constant communications with CXO( CMO, CTO, CSO,CFO and CEO), Solution Architect or System Architect, Social Media Analysts,Business Analysts,Power Users and End-Users through all possible communication channels. It is great idea to prepare a detailed plan of writing up of all necessary documents in the Project Plan. In most of the organizations and enterprises, this task is performed by a designated Project Manager.
  2. Outline Whole Requirements:
    At the beginning of Requirement Analysis, prepare an outline of requirements of Social Media Reports and Social Media Dashboard through short interaction with your System Architect or Solution Architect or Software architect, Business Analysts or Social Media Analyst, CTO or CIO, CEO and Functional Heads using all possible communication channels- Audio and Video Conferences, Enterprise Social Media, Emails, Phone And VOIP Calls and Voice Commands of HMD like Google Glass. The outcome of this analysis can be used as inputs to write report-design documents- FDS(Functional Design Specifications),DDS(Detailed Design Specifications), SRS( Software Requirement Specifications) and Test Cases. You outline the requirements of Technical Business Analysts, Business Analysts,Business Users and Functional Heads. In 2014 and beyond that, all Business Executives associated with Social Media Marketing will leverage Social Media Analytics and Social Media Dashboard in executing and formulation of Social Media Marketing Strategies. In technical side also, collect the necessary information in all aspects including an accessibility of the Reports and Dashboard on Smartphones and Mobiles.
  3. Create Use-Case Of The Requirements:
    To start the process of documentation of requirements, you create Use Cases of requirements considering all inputs finalized from the initial interactions and meetings with all associated executive including CEO. In creating the standard documents, you can use Software Design Architect Software like Visio and IBM Rational Architect. It is a great idea to have Activity Diagrams, Interactions Diagrams and Deployment Diagrams in your SRS and DDS. At end of this process, create SRS(Software Requirement Specifications) to capture the technical
    details including software architecture of your Social Media Solution.
  4. Interact With Business Users-Granulate Requirement Analysis:
    In this phase of Requirement Analysis, plan and schedule meetings and interactions with the groups of Business Users and End Users from different functional areas to gather the requirements in detail. As your requirements goes on more granularity, constantly keep on updating FDS,DDS, SRS and other relevant documents. You can leverage enterprise Email-Facilities, Phone and VOIP Calls, Enterprise Social Media Networks, Social Networks, Audio and Video Conferences and physical meetings to interact with all associated business users.
  5. Interactions With Functional Heads -Granulate Requirement Analysis:
    To conclude Requirement Analysis process, initiate interactions using enterprise Email-Facilities, Phone and VOIP Calls, Enterprise Social Media Networks, Social Networks, Audio and Video Conferences and physical meetings with the functional heads from different business departments including Finance. As your requirements goes on granularity, keep on updating DDS based on the suggestions and inputs from the functional heads. Approval of all documents by the responsible functional and technical heads and CEO can be considered as one of The Best Practices Of Designing Social Media Reports but it is not a mandatory step. Now, plan and schedule time and allocate necessary resources to design Prototype of the solution.
  6. Create Prototype Of The Solution:
    Presenting the Prototype of your solution to CXO( CMO, CTO, CSO,CFO and CEO),Solution Architect or System Architect or Software Architect, Social Media Analysts,Business Analysts,Power Users and End-Users makes the solution less error-prone.As part of this practice, utilize all points gathered inside FDS, DDS and SRS to design either HTML-based Prototype or actually working Prototype deciding based up on the suggestions from Solution Architect or System Architect or Software or yourself if you are heading the team of solution design. In designing an actually working Prototype, leverage the power and features the platform that will be deployed in the production environment.
  7. Present Your Prototype To Business Users:
    Plan and schedule an event or UWT with Coffee and Cookies Moment to present the Prototype along with all relevant documents of your Social Media Solution. It is the latest trend to present all of the requirements as an interactive Video illustrated with voice message wherever needed. During the event, collect all suggestions and Change Requests from executives of all capacities and responsibilities associated with the solution. You can schedule the ending of the event or UWT with distribution of an interactive and intuitive User Manual to CXO( CMO, CTO, CSO,CFO and CEO), Solution Architect or System Architect or Software Architect, Social Media Analysts, Business Analysts,Power Users and End-Users. Request all of them to provide feedback and suggestion for the User Manual through all possible communication channels.
  8. Update Prototype And Documents:
    Now it is time to update FDS, DDS, SRS and prototype of your solution. To executive this task, finalize all updates and suggestions collected on UWT which are necessary go inside design documents. At beginning of DDS, put the requirements summarized from FDS, update DDS and SRS with the screen-shots taken from Solution Prototype and other relevant sources, associate the additional documents and URLs inside the main documents for further references in reading the DDS during report development.
  9. Handover Prototype And Docs To Development Team:
    Take the necessary approvals before sending the documents for final approval by Business Heads and further by CTO and CEO, if it is suits in your organization hierarchy. Once approved by all necessary business and functional heads, given them to the development team in an event. Hurray!Requirement Analysis of your Social Media Reports is over!
  10. Update Documents As Changes Come-Up:
    Responsible Project Manager along with designated AMs(Assistant Managers) and Team Leaders can initiate the process of designing of reports and KPIs utilizing the inputs from Project Plan and all other necessary documents including SRS. It is always evident for noticing some of mirror updates and changes during the development phase and you constantly update them to respective documents in detail.

    Analyzed By And Author: Amrit Chhetri, Twitter: http://twitter.com/AmritChhetriB
    Place: Darjeeling-734312

Advertisements

Tagged: , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: