If you are a fresher for an IT job trials this might be useful.
Please note as per the current global IT Industry trend most of the IT organizations have moved into Agile SDLC and Continuous delivery cycles. Hence you, being fresher should be ready with this knowledge. I have made some of the below questions related to this topic.
[Also look into my old blog: https://vskumar.blog/2016/11/24/on-job-training-for-future-software-engineers-freshers-how-it-saves-their-career-time/]
SDLC AND Agile Model:
Questions on SDLC Phases:
1. What are the general phases for SDLC [Software Development Life Cycle] ?
Ans: In any development model [SDLC] following are the different phases for software delivery :
a) Requirements Investigation and analyzing
2. Where can you get requirement specifications in SDLC?
Ans: During the phase of Requirement investigation and analysis, the output will be Software Requirement Specifications. In every project during this phase user involvement is essential to get the business requirements to make the right software.
3. What is the procedure to derive the design specification?
Ans: During design phase the design specifications will be output of this activity. During this phase the final SRS is considered and it should be derived for design specification against each requirement. One requirement can have more than one design specifications. Basically you will be decomposed the software requirement into one or more design specification(s).
4. What is development or construction?
Ans: Once the design specifications have been baselined, the developer takes the design specifications to convert them into code. This activity is called constructing or developing code. The technology should be used for coding need to be specified in the design documentation. Example: Let us assume you want to develop the code in Java, so the technology should be Java.
5. What is implementation in SDLC?
Ans: The implementation activity need to be started once the code construction is completed, the code construction involves coding, code review and unit testing, integration testing. Once these 3 tasks are completed the project is moved to next phase that is implementation. During implementation phase the relevant test environment is considered for deployment of software builds for test cycles. Depends on the SDLC model; system testing and user acceptance testing can be performed, during the implementation software build can be deployed into live once the user certify UAT [User Acceptance Testing]. The Live environment is also called production environment.
6. What is the meaning for software management and retirement?
Ans: Once the software is deployed into production or live environment under first release there can be bug fixes or software enhancements; those can occur under application management life cycle and which can be a software management also. With this concept software is being upgraded during its life time. When the new technology or business systems are considered towards equivalent or more of the current software features then current software build should be retired.
Example: A mainframe [COBOL/DB2/CICS] application can be converted into windows based with Java technology. Then the existing COBOL/DB2/CICS application can be planned for a retirement with the replacement of the newly planned application. The new application can also have some more software features or the same features can be implemented.
Questions on Agile:
7. How the agile development model pulls the ideas ?
Ans: Agile development model pulls the ideas in a phased manner in the following way, by using a) Prototyping b) iterative development c) Rapid prototyping. During these phases the stakeholders or users involvement is mandatory. Their needs or suggestions also comes into the ideas for making the right software.
8. How the agile model champions the ideas?
Ans: By following various phases, different ideas are generated into the agile model. Using this approach it accelerates the software engineering team to get the right results through different software delivery iterations.
9. Why traditional approach of SDLC is not suitable for agile development model?
Ans: During the traditional approach we do not have prototyping and iterative development in the SDLC. Using the prototyping the demo can be conducted on a conceptual model of the [new or existing] software. Then the users can visualize these thoughts to extend the demo version into their live software. Then iterations comes into picture as part by part to deliver the working software in the agile development model.
To give you with some more clarity; Agile development model involves continuous construction and delivery using the phases of prototyping and iterative. For each iteration there can be prototype demonstration. Once the demo is approved the iteration will start for construction and implementation. In traditional model if we want to use for prototyping there is a phased prototype model and rapid prototype model are used, once they are approved by users the project team need to choose one of the traditional model SDLC. In this case there are two parts of delivery need to be considered where as in an agile model they are in-built for fast planning and iteration.
10. During agile model what kind of teams need to be formed to initiate the project?
Ans: To work in the agile development project we need the teams in small size, highly talented and responsive people.
11. During agile model how software requirements are considered for delivery?
Ans: Agile team needs to consider the essential, prioritized and deliverable requirements [within cycle time] from the users and construct the software in small increments those are called SPRINTS for delivery.
Next series of questions are continued……… in the below blog url:
If you are looking for any guidance please contact me and use the below Vcard: