Action Guide Reqn Spec

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Action Guide Reqn Spec - Presentation Transcript

    1. Req ‘n Spec Celeroo Builder Action Guide Development De coded
    2. What is Req ‘n Spec
      • Req ’n Spec is a crucial part of Celeroo Builder’s application development process. For that matter, it is an essential part of any software development process.
        • For applications that have more than 5 screens, we recommend that you start with the process given in this guide.
      • When do you not have to follow this process (you can then start directly at Build Pages or Build Logic modules).
        • When you are working on a one page program (like a contact form, etc.).
        • When you are working on a module that you are extremely familiar with and know that client cannot ask for too many different options (beware of making assumptions, though).
      • At other times, follow the process shown in this PPT.
    3. More on Req ‘n Spec
      • Don’t assume anything while writing spec features, however obvious it may seem, especially if it is a complex app.
      Requirement Spec Features 1 2 3
    4. Process
      • You can quickly create a new project using the button on top right corner in the Dashboard (or from the Settings tab)
      • After creating the app, click on its name to go to the App Builder module for that app.
    5. Req ‘n Spec Home
      • Here you see the various saved versions of the requirements and the users who saved them.
        • Continue saving requirements in the same version (latest) or as new versions.
        • Compare any two versions to view edits, additions and deletions.
        • These features become extremely important when you are dealing with changes and every version of this has to be signed off by you and the customer.
    6. Adding requirements
      • The customer comes to you with business requirements. These could be anywhere between an email to a detailed document with diagrams.
      • Get all your questions answered while analyzing requirements.
      • It is a good practice to write one requirement per line. Writing paragraphs will invariable cause something to be missed.
      • Don’t write detailed specifics here. You get into all the details at the feature (functional spec ) level.
    7. Tagging requirements
      • Celeroo Builder provides a highly flexible and very powerful way of managing requirements and change requests . It allows you to tag each requirement in a way that allows you to adapt it to your needs.
      • If you develop apps in phases and distribute requirements accordingly, you can tag each requirement as Phase 1, Phase 2, etc. If you follow certain Agile methodologies and use MoSCoW rules, you can tag them as Must Have, Should Have if possible, Could Have but not critical, and Won’t Have this time. You could even tag them according to what modules they fit in, e.g., Blogs, Forums, Admin, etc. Finally, if you tag it as a Change Request, you can easily filter all requirements that are part of Change Requests.
      • There is no restriction to how many tags you can have for each requirement. So, you can use them as per your needs.
    8. Features
      • Write features in as much detail as possible. As in reqs, write only one feature per bullet point. This must be very specific and should not be ambiguous or open to interpretation. Link features to requirements. Assign them to modules and pages.
      • In this step, you are creating the framework for the entire application. So, spend as much effort as needed.
    9. Defining the logic for the feature
      • Celeroo Builder offers an exciting feature where you can define what kind of a feature you are writing:
        • How does the feature affect the DB (inputs fields or data into the DB, edits data in the DB and/or displays data from it)?
        • What logic does the feature need?
        • What types of users (Admin, Visitors, Registered users, etc.) can access the feature?
      • When you build pages, build logic or assign permissions, you can sort the features by the above selections to help you easily complete that activity. For example, you can select the Inputs data into DB type features first in order to complete features that create the DB. You can then build the features that edit or display data.
    10. Traceability matrix
      • Celeroo Builder automatically creates a visual map of features and requirements when you select the requirement while writing a feature.
      • Whenever a requirement is changed, all features associated with it are highlighted to help you make necessary changes to all affected features without fail.
      • In addition, it becomes very clear both to you and the client the effort required to make such a change.
    SlideShare Zeitgeist 2009

    + celerooceleroo Nominate

    custom

    395 views, 0 favs, 2 embeds more stats

    Celeroo Builder can save around 70% of your PHP dev more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 395
      • 380 on SlideShare
      • 15 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 0
    Most viewed embeds
    • 14 views on https://www.celeroo-builder.com
    • 1 views on http://localhost

    more

    All embeds
    • 14 views on https://www.celeroo-builder.com
    • 1 views on http://localhost

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories