Showing posts with label Analysis. Show all posts
Showing posts with label Analysis. Show all posts

Sunday, January 1, 2017

Required ADDQ Archived Documents for Software Components

Required Archived Analysis-Design-Dev-QA (ADDQ) Documents for Software Components

1. Screens (Mock-up)
2. Requirements (Scenarios/User Stories)
3. Test Cases
4. UML Diagrams
5. Database Tables
6. Table Indices
7. SPs, Functions and Data Types
8. DAL Code (Data Access Layer Code)
9. BAL Code (Business Access Layer Code)
10. PL Code (Presentation Layer Code - Code Behind Page)
11. Logging Code
12. CL Script and Markup (CL: Client Layer/Client Side)
13. CL Rendered Source 
14. ML Input Code and Script (ML: Machine Learning)
15. ML Process Code
16. ML Output Code

17. ML Presentation Code
18. ML Sync Integrity Code
19. Help/Wiki
20. Next Version Requirements


 



 
 
 






Friday, August 28, 2015

INTERVIEW :: ANALYSIS :: MODELING :: UML



INTERVIEW
  ANALYSIS
    MODELING
      UML

In which of the following diagrams, would you define signatures for the methods?

Use Case Diagram
Class Diagram
Object Diagram
State Diagram
Sequence Diagram
Collaboration Diagram
Activity Diagram
Deployment Diagram
Component Diagram
 



Thursday, August 27, 2015

INTERVIEW :: ANALYSIS/DEVELOPMENT :: PROCESS STEPS (PHASES) :: SDLC


INTERVIEW
  ANALYSIS/DEVELOPMENT
    PROCESS STEPS (PHASES)
      SDLC


How do you improve the following steps to cover SDLC?

Step 1: Plot (Defining/Planning + Mockup Screens)


Step 2: Requirement Analysis [+ Modeling]


Step 3: Logical Design/System Analysis [+ Modeling]


Step 4: Physical Design/System Design [+ Modeling]


Step 5: UI Design


Step 6: Development


Step 7: Test


Step 8: Deployment


Step 9: Maintenance ==> Evolution: Go To Step 1 or 2.