From our professor:Course Policies
Discussions
Every student is expected to participate in the discussion by contributing a posting (Primary
Post) of 150 – 200 words about topic in the forum, and at least one (1) responses (replies) to
other students’ posting. There is, of course, no upper limit on the level of your participation
in the discussion.
I recommend that you print a copy of your postings to keep as a log of your participation in
the discussion forum. Since the quality of the content and format of your posting is
important, it is also recommended that you write your submission in a word processor, save
the file on your disk, then copy and paste the text in the discussion area. That way you have
an archive of your postings. This is our way of sharing our ideas and information.
I will NOT respond to every posting that is made, but will make comments when
appropriate. Please note that I plan to read every word posted in any section of this class
web site by students. Since there are only two posts required – please do not simply post as
“I agree”, when I look at a response I want to see if the thread can be continued. For
example, having a discussion with your friends, you can even ask a question, pose a
problem, or change the focus of the response, something that two people in a conversation
could continue.
The University is committed to open, frank, and insightful dialogue in all of its courses.
Diversity has many manifestations including diversity of thought, opinion and values. We
encourage all learners to be respectful of that diversity and to refrain from inappropriate
commentary. Should such inappropriate comments occur, the instructors will intervene as
they monitor the dialogue in each of their courses. I would expect our discussions to be
lively and informative. Again, don’t make comments that you cannot back up with research
and references for your postings.
……………………………………………………………………………………………………..
From our professor:
Week 10 Objectives
Reflect on our learnings of system analysis and design
Week 10 System Analysis Tips and Tricks / Wrap-up
In During this term we talked a lot about system analysis and design, looked at many
examples, and saw just how many areas we have to be aware of in designing a system
Are there any tips we could walk away with, e.g., what do you believe is necessary for
good system analysis and design?
Responed to this:
A phase-based approach to system design by using the systems development life cycle
(SDLC) or data science life cycle is essential to ensure a quality system for deployment.
Throughout the course we covered different phases of the data science life cycle from
Cybrary each week and it highlighted the importance of adhering to a life cycle. Each phase
outlines critical goals to guarantee the system’s purpose is met and functions over time.
Under SDLC these phases include requirements analysis, design, development, testing,
implementation, and maintenance (documentation and evaluation).
Although following a structured phase-based approach to developing a system will require
immense resources, it pays off because the system can adapt (to a degree) as technology
ages. Using something like SDLC allows for quicker turnover for things like troubleshooting
bugs in the system because it should be well documented. The data science life cycle allows
for constant iterations which improves the model by updating data and refines an
organization’s knowledge.