Scribd Logo
Încărcați

Bine ați venit la Scribd!

  • Tgmc2010 Scenario - Template

    Încărcat de

    Thilak Kumar
    84 vizualizări2 pagini
    Project Scenario Template - The Great Mind Challenge. I. Name of the Project Objective / Vision users of the System ii. Iii. Functional iv. Requirements v. (Atleast Eight) vi. Vii. Viii. Secure access of confidential data (user's details). SSL can be used.

    Descriere originală:

    Drepturi de autor

    © Attribution Non-Commercial (BY-NC)

    Formate disponibile

    DOC, PDF, TXT sau citiți online pe Scribd

    Vi se pare util acest document?

    Este necorespunzător acest conținut?

    Raportați acest document
    Project Scenario Template - The Great Mind Challenge. I. Name of the Project Objective / Vision users of the System ii. Iii. Functional iv. Requirements v. (Atleast Eight) vi. Vii. Viii. Secure access of confidential data (user's details). SSL can be used.

    Drepturi de autor:

    Attribution Non-Commercial (BY-NC)
    Descărcați ca DOC, PDF, TXT sau citiți online pe Scribd
    Indicator pentru conținut neadecvat
    84 vizualizări2 pagini

    Tgmc2010 Scenario - Template

    Încărcat de

    Thilak Kumar
    Project Scenario Template - The Great Mind Challenge. I. Name of the Project Objective / Vision users of the System ii. Iii. Functional iv. Requirements v. (Atleast Eight) vi. Vii. Viii. Secure access of confidential data (user's details). SSL can be used.

    Drepturi de autor:

    Attribution Non-Commercial (BY-NC)
    Descărcați ca DOC, PDF, TXT sau citiți online pe Scribd
    Indicator pentru conținut neadecvat
    din 2

    The Great Mind Challenge - Project Scenario Template

    Note: Already filled information should not be changed


    Name of the
    1.
    Project

    Objective/
    2.
    Vision

    A.
    Users of the B.
    3.
    System C.
    D.

    i.
    ii.
    iii.
    Functional
    iv.
    4. Requirements
    v.
    (Atleast Eight)
    vi.
    vii.
    viii.

    i. Secure access of confidential data (user’s


    details). SSL can be used.
    Non-functional ii. 24 X 7 availability
    5. requirements iii. Better component design to get better
    (Atleast Four) performance at peak time
    iv. Flexible service based architecture will be
    highly desirable for future extension

    a.
    Optional
    6. b.
    features
    c.

    A. Professional look and feel


    B. Use of AJAX atleast with all registration forms
    C. Browser testing and support for IE, NN, Mozila,
    User interface and Firefox.
    7.
    priorities D. Use of Graphical tool like JASPER to show
    strategic data to admin
    E. Reports exportable in .XLS, .PDF or any other
    desirable format
    A.
    B.
    8. Reports
    C.
    D.
    Other important A.
    9.
    issues B.
    10. Team Size 4
    Technologies to UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-
    11.
    be used services, SOA
    • ROSE/RSA / WebSphere Modeler
    • Eclipse/ RAD / Lotus Forms Designer / Portlet
    Factory
    12. Tools to be Used • WebSphere Portal/ WAS/ WAS CE / WPS
    • DB2 Express – ‘C’ or DB2 UDB
    • Tivoli CDP/TSM / Tivoli Directory Server
    • Linux will be the preferred OS.
    A. Online or offline help to above said users,
    Application deployment executive and
    Final developer
    13. Deliverable B. Application archive ( .war/.ear ) with source
    must include code
    C. Database backup and DDL Script
    D. Complete Source code

    S-ar putea să vă placă și