sikeveo
back after sem2
Is creating a data dictionary part of the implementation stage or planning and designing?
Implementation (1 Viewer)
- Thread starter sikeveo
- Start date
sikeveo
back after sem2
I remember reading it somewhere, hence my question.
sikeveo
back after sem2
Sorry Casmira. Creating the data dictionary is part of the implementation stage according to the independant trial marking guidelines.
No, its done in the modelling stage which falls under planning and design
here is an excerpt of my notes
=============
[Implementation]
– technical documentation, including
This sort of documentation is for programmers, developers and analysts to modify or reconstruct the program, it consists of;
Source code helps developers understand the programs function
* Algorithms clearly identify the steps the program takes to carry out a task and helps identify a programs structure.
* Data dictionary used to describe each data item as much as possible, which is the input data
* Systems documentation includes the systems flowchart, and dataflow diagrams to help understand the hardware and software configuration to which the program was designed for.
=============
I just keep thinking data dictionary isn't made because its only mentioned in implementation as what should consist of technical documentation- however its actually created in the earlier stages, refer to my first post, why make data dictionary in the middle of coding?
edit: further clarification
here is syllabus excerpt from planning and design
=============
Documentation of the overall software solution
• tools for representing a complex software solution include:
– algorithm descriptions
– system flowcharts
– structure diagrams
– data flow diagrams
– data dictionary
=============
essentially, you represent a system (ie. model, create, draw, structure) using some lovely diagrams, and a magical data dictionary
and in implementation;
=============
Documentation of a software solution
• forms of documentation, including:
– process diary
– user documentation
– self-documentation of the code
– technical documentation, including source code, algorithms, data dictionary and systems documentation
– documentation for subsequent maintenance of the code
=============
using common sense, its obvious that algorithms and data dictionary have been made before the program has been made, the reason you make a data dictionary is to keep track the proposed variables/identifiers (and that sort of shit), so once you manage to implement/code/write the program that you have in mind what to do, what is the use of a data dictionary in the middle of coding, or lets just assume after? I understand you can make it in the middle of programming, sure you can, but the development cycle has distinctive steps that state "certain shit will be performed here"
now since we are taught the structured development cycle indetail, it clearly states each stage has its own little unique specialised task, ie. defining and understanding involves nagging clients as to what they want, planning and design basically plans and designs the system (ironically) in which data dictionary is done, implementation is compiling the code and sofourth (we're taught other shit but you know)
here is an excerpt of my notes
=============
[Implementation]
– technical documentation, including
This sort of documentation is for programmers, developers and analysts to modify or reconstruct the program, it consists of;
Source code helps developers understand the programs function
* Algorithms clearly identify the steps the program takes to carry out a task and helps identify a programs structure.
* Data dictionary used to describe each data item as much as possible, which is the input data
* Systems documentation includes the systems flowchart, and dataflow diagrams to help understand the hardware and software configuration to which the program was designed for.
=============
I just keep thinking data dictionary isn't made because its only mentioned in implementation as what should consist of technical documentation- however its actually created in the earlier stages, refer to my first post, why make data dictionary in the middle of coding?
edit: further clarification
here is syllabus excerpt from planning and design
=============
Documentation of the overall software solution
• tools for representing a complex software solution include:
– algorithm descriptions
– system flowcharts
– structure diagrams
– data flow diagrams
– data dictionary
=============
essentially, you represent a system (ie. model, create, draw, structure) using some lovely diagrams, and a magical data dictionary
and in implementation;
=============
Documentation of a software solution
• forms of documentation, including:
– process diary
– user documentation
– self-documentation of the code
– technical documentation, including source code, algorithms, data dictionary and systems documentation
– documentation for subsequent maintenance of the code
=============
using common sense, its obvious that algorithms and data dictionary have been made before the program has been made, the reason you make a data dictionary is to keep track the proposed variables/identifiers (and that sort of shit), so once you manage to implement/code/write the program that you have in mind what to do, what is the use of a data dictionary in the middle of coding, or lets just assume after? I understand you can make it in the middle of programming, sure you can, but the development cycle has distinctive steps that state "certain shit will be performed here"
now since we are taught the structured development cycle indetail, it clearly states each stage has its own little unique specialised task, ie. defining and understanding involves nagging clients as to what they want, planning and design basically plans and designs the system (ironically) in which data dictionary is done, implementation is compiling the code and sofourth (we're taught other shit but you know)
Last edited:
sikeveo
back after sem2
Sorry Casmira. SamD's book contradicts your notes, as do the independant trial marking guidelines.
Bunny04
VIVE LA FRANCE
- Joined
- Oct 18, 2004
- Messages
- 995
- Gender
- Female
- HSC
- 2004
Woot- i remember this from when i did SDD for the hsc... and i'm pretty sure Casmira is right..
its a tool used in 'Planning and Design' seeing as its the foundation for most programs.. all though, you could put it under iMplementation.. Oh gawd, im confusing myself again...
its a tool used in 'Planning and Design' seeing as its the foundation for most programs.. all though, you could put it under iMplementation.. Oh gawd, im confusing myself again...
sikeveo
back after sem2
Check in SamD's book.
This
"Documentation
• types of documentation
– documentation for developers
– documentation for users
• internal documentation
– meaningful variable names (intrinsic)
– readability of code (comments, white space and indentation)
• online help"
Is under "8.2.2 Building software solutions" on page 24 of the syllabus.
This
"Documentation
• types of documentation
– documentation for developers
– documentation for users
• internal documentation
– meaningful variable names (intrinsic)
– readability of code (comments, white space and indentation)
• online help"
Is under "8.2.2 Building software solutions" on page 24 of the syllabus.
Bunny04
VIVE LA FRANCE
- Joined
- Oct 18, 2004
- Messages
- 995
- Gender
- Female
- HSC
- 2004
hang on... it IS part of documentation.. I swear... -ish still confused, but things are comming back-
sikeveo
back after sem2
Documentation is part of the Implementation stage.
Tools need not be part of only one stage. Software development is an ongoing process of change and refinement. If you are talking about creating a data dictionary, then this is most definitely done in the planning stage, as you cannot start any type of implementation before you are yet to even define what data elements you are using and their interactions. Similarly documentation isnt limited to the implementation stage, it occurs in most of the stages as you would see in any project that is well planned.
sikeveo
back after sem2
I see your point acmilan, however the syllabus states my viewpoint explicity as does the independant trial marking guidelines.
Where can i get clarification?
Where can i get clarification?
isn't that the preliminary course?sikeveo said:
User documentation and some technical documentation is, refer to belowsikeveo said:
======================
Documentation of a software
solution
• forms of documentation, including:
– process diary
– user documentation
– self-documentation of the code
– technical documentation, including source code, algorithms, data
dictionary and systems documentation
– documentation for subsequent maintenance of the code
• use of application software to assist in the documentation process
– use of CASE tools
======================
The only technical documentation that's made during implementation is source code, systems documentation (eg. intrinsic code)
Correct, but even if we did anything to the the data dictionary throughout any stage past planning and design, it would be modified, its actual creation is in planning and designacmilan said:
Last edited:
sikeveo
back after sem2
Meh i dont really care now. Got the mark anyway.
sikeveo
back after sem2
lol. Good revision anyway.
data dictionaries are contained in both the planning stage and the implementation stage.
from the syllabus:-
9.2.3 Implementation of software solutions
Students Learn About
Documentation of a software
solution
• forms of documentation, including:
– process diary
– user documentation
– self-documentation of the code
– technical documentation, including
source code, algorithms, data
dictionary and systems
documentation
– documentation for subsequent
maintenance of the code
• use of application software to assist
in the documentation process
– use of CASE tools
and in
9.2.2 Planning and design of software solutions
Students Learn About
Documentation of the overall
software solution
• tools for representing a complex
software solution include:
– algorithm descriptions
– system flowcharts
– structure diagrams
– data flow diagrams
– data dictionary
Therefore data dictionaries are part of BOTH implementation and planning stages of the software cycle, according to the syllabus.
sorry to shatter your ego Casmira
from the syllabus:-
9.2.3 Implementation of software solutions
Students Learn About
Documentation of a software
solution
• forms of documentation, including:
– process diary
– user documentation
– self-documentation of the code
– technical documentation, including
source code, algorithms, data
dictionary and systems
documentation
– documentation for subsequent
maintenance of the code
• use of application software to assist
in the documentation process
– use of CASE tools
and in
9.2.2 Planning and design of software solutions
Students Learn About
Documentation of the overall
software solution
• tools for representing a complex
software solution include:
– algorithm descriptions
– system flowcharts
– structure diagrams
– data flow diagrams
– data dictionary
Therefore data dictionaries are part of BOTH implementation and planning stages of the software cycle, according to the syllabus.
sorry to shatter your ego Casmira