View previous topic :: View next topic
|
Author |
Message |
palaveerareddy
New User
Joined: 13 Apr 2005 Posts: 5
|
|
|
|
I was asked in accenture interview:
- 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?
p.v.reddy |
|
Back to top |
|
|
jagadish2005
New User
Joined: 08 Mar 2005 Posts: 20
|
|
|
|
Hi,
I saw ur question:
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
With regards
arunachalla |
|
Back to top |
|
|
palaveerareddy
New User
Joined: 13 Apr 2005 Posts: 5
|
|
|
|
hi
thanx for your reply
can you give elaborate answer.
do you mean low level specifications are list of impacted programs due to some change. please give full details with an example.
thanks in advance
p.v.reddy |
|
Back to top |
|
|
thatiparthis
New User
Joined: 02 Jun 2003 Posts: 5 Location: Chennai - India
|
|
|
|
Who the heck had suggested that low level specifications are list of impacted programs ??
If you dont know - tell dont know - but dont misguide others !!!
That IP Art is HIS !! |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
|
|
thatiparthis......
There is a BLUE Button with each & every reply posted. If you are not agree with any one. You suppose to use the same.
Quote: |
Who the heck had suggested that low level specifications are list of impacted programs ??
If you dont know - tell dont know - but dont misguide others !!! |
Please be a bit graceful to others who are putting their time & effort here.
Thanks & Regards,
Priyesh. |
|
Back to top |
|
|
jagadish2005
New User
Joined: 08 Mar 2005 Posts: 20
|
|
|
|
[quote="priyesh.agrawal"]thatiparthis......
There is a BLUE Button with each & every reply posted. If you are not agree with any one. You suppose to use the same.
[quote]Who the heck had suggested that low level specifications are list of impacted programs ??
If you dont know - tell dont know - but dont misguide others !!! [/quote]
Please be a bit graceful to others who are putting their time & effort here.
Thanks & Regards,
Priyesh.[/quote]
Hi thatiparthis,
I saw ur reply I hope u totally misunderstanded . I hope so u never worked in developement / echancement project . Mostly low level specification is anything but specifying which programs whether were impacted & which programs were are not impacted under ur the module in a document . IF u take impacted programs u specifying whether it is statically / dynamically in that document . For these programs if itis dynamically affecting == u will specifying approcah , statically affecting ==
u will spectifying certain approach
With regards
arunachalla |
|
Back to top |
|
|
ratheesh
New User
Joined: 30 Jun 2005 Posts: 1
|
|
|
|
what is meant by impacted programs?plz explain? |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
|
|
Hi ratheesh,
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.
Enhancements are welcome.
Regards,
Priyesh. |
|
Back to top |
|
|
Cartraga
New User
Joined: 13 May 2005 Posts: 4
|
|
|
|
Hi
This is what i found reg. High and Low level ones,
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).
Pls give feedback or correct me if i am wrong.
Regards,
CRT |
|
Back to top |
|
|
|