Tuesday, August 16, 2011

L2 principles of software engineering?

So here's what i wiki-ed:
Software Engineering (SE) is a profession dedicated to designing, implementing, and modifying software so that it is of high quality, affordable, maintainable, and fast to build. It is a "systematic approach to the analysis, design, assessment, implementation, test, maintenance and reengineering of software, that is, the application of engineering to software."
Lecture wasn't a dry and boring one. It kind of summarized and simplified alot of complicated info into a simple presentation + sharing session from seniors (to suit non programemrs ^.^).

Key take-aways

1) SE involves Process, Programming,People. In our class, mostly are programmers & designers. Programmers are the core drivers of a project i would say, cause any app would require them to churn out all the complicated system. While the designers are the ones that make the outlook of the app pretty and easy to navigate for users.

2) Software development life cycle (SDLC) is somewhat similar to design iterations taught in previous design modules I took.

Iterative design is based on a cyclic process of prototyping, testing, analyzing and refining. Changes should be made according to feedback and thus the process helps to improve the quality and functionality of a design.


3) Decomposition | Abstraction | Design for Change

4) What I found interesting is the "High Cohesion, Low Coupling" theory. Cohesion i understand. Each module should be highly cohesive such that components are closely related and meaningful. But Low Coupling is kinda different from what i learn from Comms which is always stressing in the importance of making lotsa interactions with people. Everyone talks about networking and based on social networks, everyone is linked together. "6 Degrees of separation" proves that. We have been to told to tt interaction good, thus, without much thoughts, i chose the first diagram in my heart Prof Ben asked in class.



Based the programming pov, perhaps we can reflect abit more and probably too much connections with other people ain't good afterall.

On the side note! I created a foursquare venue for SR@LT19! LOL. Im gonna check in every single time and be the mayor! woohoo!

6 comments:

  1. nice interesting post on software development. Even as a computing student I also learnt a few new things. Good analysis

    ReplyDelete
  2. I have a question: what's up with foursquare? Why do people like to check in and become mayor? Fun meh? :-P

    ReplyDelete
  3. It was fun. Because there is more credibility being a mayor when you are reviewing the food.

    ReplyDelete
  4. Hehe! In a way it helps the STM me to rmb i go and of course we r kinda ruled by foursquare's gamification!!!! "BADGESS" AND "MAYORSHIP"~~~

    ReplyDelete
  5. Thanks. I was quite perplexed when I couldn't find a foursquare location @ SR@LT19

    ReplyDelete
  6. hehehe wa! meaning now gotta fight for mayorship HEE :)

    ReplyDelete