GAVS Welcomes you to the formative assessment on the topic Process & Methods
Supplier Input Process Output Customer
System Input Process Output Client
System Input Process Output Customer
System
Supplier
Input
Output
Process
Customer
Understanding / Analyzing the requirement prior to start coding
Escalating technical issues directly to Project Manager
Construct code as per coding standards applicable for the technology including security standards
Escalate to Team Lead when a technical problem is not resolved by myself
Reporting the actual effort spent and status of activities through timesheet system
Asking Questions / Queries to Team Lead / Immediate supervisor related to tasks / requirements
Doing a CAR and DAR
Business Management Service
Business Management Support
Business Management System
Infrastructure Managed Services
Infrastructure Management System
Infrastructure Management Software
Product Owner
Scrum Master
Quality Assurance
Client
As soon as Code is complete, because it is agile
End of successful build
End of each sprint or iteration
At the end of every month
At the end of each sprint
As and when Team Lead or Project Manager inform me
Daily
Weekly
Complete system / application
Integrated modules
Individual components
Performance Test
System Test
Regression Test
Unit Test
Defect Tracking tool
Verbally
In person
Update the status in the defect tracking tool
Report the status to Team Lead in person
Send an email to Team Lead listing all the review feedback and it's status
As per the process applicable for my project
Project speciic process
ISO Process
BMS Process
CMMi Process
Report actual effort spent for coding
Report estimated effort as the actual effort spent
Report the actual effort spent for coding including fixing defects
Do a Root cause analysis or causal analysis report
Do decision analysis and prepare DAR repport
Try to resolve the problem first and then approach immediate supervisor seeking for help
True
False
True
False
True
False
When a project is failed
When more number of defects detected in the software application
For assigning tasks
None of the above
Creating a new program
Fixing a defect and or Incorporating an enhancement
Answering to queries raised by client
Only answer to queries raised by client - Fixing a defect is not my responsibility
Injection
Cross-Site Scripting
Broken Authentication and Session Management
Insecure Direct Object References
Security Misconfiguration
Sensitive Data Exposure
Missing function level access control
Using components with Known vulnerabilities
Unvalidated redirects and forwards
Un-encrypted Passwords
Unstructured coding practice
True
False
All fields level validation, if else, case statements and branching / calling programs are tested
Test the output with the system requirement specification given by TL with Test cases
Keep quite until some one ask question
keep quite when I don't know the answer for the question directed to me
Keep quite even if know the answer partially
Explain to the extend that I know for the question directed to me
Mention issue id / defect id in the version control tool while check-in
Mention the change request no. in the version control tool while check-in
No need to mention any message
Option4
Wait!
Here's an interesting quiz for you.