Tag: #teamwork
UML
Team talk about Agile Development
Today on Ken´s Class we talked about Agile Development.
Agile Development is a methodology that was presented in the Agile Manifesto wrote in 2001. Gerardo Juarez and me discussed about the main principles about Agile Development presented in the manifesto. Agile Development was made to make the process of developing a software faster with only the functionla part, it is also about group collaboration and open communication with the customer.
The Agile Manifesto propose 12 principles to follow this methodology:
- Customer satisfaction by early and continuous delivery of valuable software
- Welcome changing requirements, even in late development
- Working software is delivered frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Face-to-face conversation is the best form of communication (co-location)
- Working software is the principal measure of progress
- Sustainable development, able to maintain a constant pace
- Continuous attention to technical excellence and good design
- Simplicity—the art of maximizing the amount of work not done—is essential
- Best architectures, requirements, and designs emerge from self-organizing teams
- Regularly, the team reflects on how to become more effective, and adjusts accordingly
We think that Agile Development is very useful because it is about delivering only the functional part of the software, the design comes later, the simpliest the better. It is also useful when the customer is not sure about what he/she wants because it allows the team to change constantly during the elaboration of the program. Some disadvantages that some people

Team talk about Agile Development
Today on Ken´s Class we talked about Agile Development.
Agile Development is a methodology that was presented in the Agile Manifesto wrote in 2001. Gerardo Juarez and me discussed about the main principles about Agile Development presented in the manifesto. Agile Development was made to make the process of developing a software faster with only the functionla part, it is also about group collaboration and open communication with the customer.
The Agile Manifesto propose 12 principles to follow this methodology:
- Customer satisfaction by early and continuous delivery of valuable software
- Welcome changing requirements, even in late development
- Working software is delivered frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Face-to-face conversation is the best form of communication (co-location)
- Working software is the principal measure of progress
- Sustainable development, able to maintain a constant pace
- Continuous attention to technical excellence and good design
- Simplicity—the art of maximizing the amount of work not done—is essential
- Best architectures, requirements, and designs emerge from self-organizing teams
- Regularly, the team reflects on how to become more effective, and adjusts accordingly
We think that Agile Development is very useful because it is about delivering only the functional part of the software, the design comes later, the simpliest the better. It is also useful when the customer is not sure about what he/she wants because it allows the team to change constantly during the elaboration of the program. Some disadvantages that some people

Group talk about Ethics in Software Engineering
Today we talked about ethics in ken´s class.
Frida, Sara, José Manuel, Estefy, Hermes and me discussed what are ethics and why we need them while making software.Ethics are important in software engineering because they contribute to society and human well-being, be honest and trusworthly, be fair, honor property rights, respect privacy and in general have a good professional conduct.
Software engineering ethics are based on 8 principles that were principaly made to avoid harming others:
-Public
-Client and employer
-Product
-Judgement
-Management
-Profession
-Coleagues
-Self
We discussed a really important point about this, some said that the code of ethics is not a code of rules, it´s just made to suggest a proper conduct but following it or not is an obligation. I personally think that this depends on the place you are working, some companies care about their public image and they will fire you if they notice that you are doing something unethical, but others don´t care if they are harming others with their products and sometimes promote unethical software (see malware). Of course, it is optimal that every software engineer follow the code of ethics as a personal way of living but in reality some people and companies just care for money and they don´t care if they are doing something unethical as long as they are winning more.
Discipline vs Art
Software engineering is the last engineering created, but it will be the base for future careers that will change the way we see the world now. It’s different from others because you may get a virtual result that will function in real life and not necessary tangible one.
Software engineers can create something with a single a computer, and their limits are only the limits that they give themselves.
Making software is not just programming; there’s a processes of planing before creating something and a process of improving it after you created it. But it’s always better to develop something that comes from our imagination, in that way we convert a piece of software into a piece of art.
Collaboration:
Victor A. Najar
Miguel A. Cabral
Ramón García
Michelle Sagnelli
