1)Tell me about your project
Ans: Explain about your project (client location, business requirement, team size and roles and responsibilities).
2)Tell what is the recent change request you have got?
Ans: Tell one business requirement, which is related to the your code. How could you code, what cycle process you implemented your code. From the FRD to End everything you should explain step by step.
3)What are the difficulties you faced?
Ans: If any requirement you didn't understand (or) If existed code is very difficult to understand etc....
4)What are the abend codes you got and how you resolved them
Impacted Program : What I understand with this term is the module or program which is going to get affected, If changing/updating any thing (source).
Simply ...If PROG A is calling PROG B. & you are going to make some changes in PROG B, Impacted one would be PROG A.
There might be some other standard/more specific definition.
High Level specifications consist of required properties ( I need to add two columns for holding this and this data).
Low Level specifications consist of primitive needs and conditions used by these high level specifications ( The data will have to be related to this data, should get deleted when its parent data gets deleted).
Regarding the Functional and technical ones
Functional specification defines how the change( in this case case the two columns) will serve functionally (whether a person can update or delete the data, duplicates can exist or not, if somebody enters the wrong data into those columns what shd happen)
Technical specification is the one which describes how the change is to be done technically( what is the datatype to be entered, whether it should accept null values or not).
Soc4, Soc7, Space abend (SB37, SD37, SE37), 811, 803, S322 etc....
5) what are low level specifications, high level specifications
technical specifications and functional specifications?
what do they consist of?
- if I add two columns to table how these specificatiions will be affected?
1. high level specifications: over all module spec. / design
2. low level specifications: total no of application prog impacting document
3. technical specifications : each application prog spec / design
4. functional specifications: if there is any online cics prog , any new field to be added in screen , whether functionally of that is going to change or not
- what do they consist of?
if I add two columns to table how these specificatiions will be affected? :
mostly it will affect low level design / tech spect . check whether it is affecting statically / dynamically
Ans: Explain about your project (client location, business requirement, team size and roles and responsibilities).
2)Tell what is the recent change request you have got?
Ans: Tell one business requirement, which is related to the your code. How could you code, what cycle process you implemented your code. From the FRD to End everything you should explain step by step.
3)What are the difficulties you faced?
Ans: If any requirement you didn't understand (or) If existed code is very difficult to understand etc....
4)What are the abend codes you got and how you resolved them
Impacted Program : What I understand with this term is the module or program which is going to get affected, If changing/updating any thing (source).
Simply ...If PROG A is calling PROG B. & you are going to make some changes in PROG B, Impacted one would be PROG A.
There might be some other standard/more specific definition.
High Level specifications consist of required properties ( I need to add two columns for holding this and this data).
Low Level specifications consist of primitive needs and conditions used by these high level specifications ( The data will have to be related to this data, should get deleted when its parent data gets deleted).
Regarding the Functional and technical ones
Functional specification defines how the change( in this case case the two columns) will serve functionally (whether a person can update or delete the data, duplicates can exist or not, if somebody enters the wrong data into those columns what shd happen)
Technical specification is the one which describes how the change is to be done technically( what is the datatype to be entered, whether it should accept null values or not).
Soc4, Soc7, Space abend (SB37, SD37, SE37), 811, 803, S322 etc....
5) what are low level specifications, high level specifications
technical specifications and functional specifications?
what do they consist of?
- if I add two columns to table how these specificatiions will be affected?
1. high level specifications: over all module spec. / design
2. low level specifications: total no of application prog impacting document
3. technical specifications : each application prog spec / design
4. functional specifications: if there is any online cics prog , any new field to be added in screen , whether functionally of that is going to change or not
- what do they consist of?
if I add two columns to table how these specificatiions will be affected? :
mostly it will affect low level design / tech spect . check whether it is affecting statically / dynamically
No comments:
Post a Comment